Security Resilience

CVE-2024-6313

Published
09 July 2024
Modified
15 April 2026
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.011 66th percentile
Risk Priority 86 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-6313 is a critical-severity Unrestricted Upload of File with Dangerous Type (CWE-434) vulnerability in Wordpress (inferred from references). Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Web Shell (T1505.003); ranked in the top 34% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-3 (Malicious Code Protection) and CM-7 (Least Functionality) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

The Gutenberg Forms plugin for WordPress, in versions up to and including 2.2.9, contains an arbitrary file upload vulnerability (CWE-434) in the upload handling logic. The affected code in Bucket.php and email.php allows users to specify permitted file types without sufficient server-side validation or restriction, enabling uploads of any file to the site server.

Unauthenticated attackers can exploit the flaw over the network by submitting crafted form uploads that bypass the type checks. Successful exploitation grants the ability to place arbitrary files, including web shells, on the target server and achieve remote code execution with full confidentiality, integrity, and availability impact, as reflected in the CVSS 9.8 score.

EPSS for the CVE rose from a low baseline to a peak of 0.2971 on 2025-12-11 before receding to the current value of 0.2319, indicating measurable post-disclosure exploitation interest. The referenced advisories and code traces from Wordfence and the WordPress plugin repository highlight the vulnerable functions but do not detail a specific patched version or mitigation steps beyond the need to address the upload controls.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The Gutenberg Forms plugin for WordPress is vulnerable to arbitrary file uploads due to the users can specify the allowed file types in the 'upload' function in versions up to, and including, 2.2.9. This makes it possible for unauthenticated attackers…

more

to upload arbitrary files on the affected site's server which may make remote code execution possible.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1505.003 Web Shell Persistence
Adversaries may backdoor web servers with web shells to establish persistent access to systems.
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1505 Server Software Component Persistence
Adversaries may abuse legitimate extensible development features of servers to establish persistent access to systems.
T1105 Ingress Tool Transfer Command And Control
Adversaries may transfer tools or other files from an external system into a compromised environment.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-29848Shared CWE-434
CVE-2024-5049Shared CWE-434
CVE-2023-2063Shared CWE-434
CVE-2018-25436Shared CWE-434
CVE-2026-92980Shared CWE-434
CVE-2023-26762Shared CWE-434
CVE-2024-1921Shared CWE-434
CVE-2023-39346Shared CWE-434
CVE-2025-32291Shared CWE-434
CVE-2023-29384Shared CWE-434

Affected Assets

Wordpress
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.1.1

Mitigating Controls (NIST 800-53 r5) AI

Malicious-code protection at entry points blocks dangerous file types from being accepted and executed.

Least functionality restricts the file types and automatic processing capabilities the system will accept.

SC-18 Mobile Code partial match

Mobile-code controls define, authorize, and block unacceptable uploaded code before automatic processing occurs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-05 mostly match
blocks

Restricting execution of unauthorized software directly blocks dangerous uploaded files from running.

PR.PS-01 partial match
blocks

Hardened configuration baselines can enforce allowed file types and processing rules.

PR.PS-06 partial match
blocks

Secure development practices include input validation and file-type restrictions that prevent this weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Configuration and acceptance testing verify that file-upload handling enforces allowed types and does not permit dangerous content to be stored or executed.

References