Cyber Resilience

CVE-2024-11613

RCE in Iptanus Wordpress File Upload ≤ 4.25.0

Published
08 January 2025
Modified
08 April 2026
Patch / advisory
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.044 90th percentile
Risk Priority 97 floored blend · peak EPSS

Summary

CVE-2024-11613 is a critical-severity Code Injection (CWE-94) vulnerability in Iptanus Wordpress File Upload. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 10% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — 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 WordPress File Upload plugin for WordPress is vulnerable to remote code execution, arbitrary file read, and arbitrary file deletion in all versions through 4.24.15. The issue resides in wfu_file_downloader.php, where insufficient sanitization of the user-supplied “source” parameter permits an attacker-controlled directory path, enabling the flaws tracked under CWE-94.

Unauthenticated attackers can exploit the vulnerability over the network to upload and execute arbitrary code, read sensitive files, or delete arbitrary files on the server, resulting in full compromise as reflected by the CVSS 9.8 score.

Public references point to a fix committed in changeset 3217005 of the plugin repository and to detailed analysis published by Abra Hack and Wordfence; administrators should update to a patched release once available through the WordPress plugin directory.

The associated EPSS score has remained near 0.79 since disclosure, indicating sustained exploitation interest without evidence of a sharp post-publication climb.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The WordPress File Upload plugin for WordPress is vulnerable to Remote Code Execution, Arbitrary File Read, and Arbitrary File Deletion in all versions up to, and including, 4.24.15 via the 'wfu_file_downloader.php' file. This is due to lack of proper sanitization…

more

of the 'source' parameter and allowing a user-defined directory path. This makes it possible for unauthenticated attackers to execute code on the server.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
T1059.002 AppleScript Execution
Adversaries may abuse AppleScript for execution.
T1059.004 Unix Shell Execution
Adversaries may abuse Unix shell commands and scripts for execution.
T1059.005 Visual Basic Execution
Adversaries may abuse Visual Basic (VB) for execution.
T1059.006 Python Execution
Adversaries may abuse Python commands and scripts for execution.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-11635Same product: Iptanus Wordpress File Upload
CVE-2024-2847Same product: Iptanus Wordpress File Upload
CVE-2023-4811Same product: Iptanus Wordpress File Upload
CVE-2023-2688Same product: Iptanus Wordpress File Upload
CVE-2023-2767Same product: Iptanus Wordpress File Upload
CVE-2024-50450Same product class: CMS core
CVE-2018-7602Same product class: CMS core
CVE-2024-56051Same product class: CMS core
CVE-2024-22188Same product class: CMS core
CVE-2023-40606Same product class: CMS core

Affected Assets

iptanus
wordpress file upload
≤ 4.25.0

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)
  • V1.3.1

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation finds code paths that accept and execute externally influenced strings.

Input validation directly stops untrusted data from being used to construct executable code without neutralization.

Least privilege limits the damage an injected code fragment can perform once executed.

Requiring documented secure development standards and tools enforces use of safe code-generation APIs and escaping.

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-06 mostly match
prevents

PR.PS-06's SDLC practices directly target injection flaws via secure coding and testing (mostly), yet as a single broad outcome it leaves many code-generation specifics unaddressed (partial).

PR.DS-10 none match
prevents

PR.DS-10 protects runtime data confidentiality/integrity but has no bearing on neutralizing externally influenced input during code generation, so neither direction shows any preventive effect.

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.

prevents

Banning unapproved code samples and unauthenticated web services, combined with secure-coding standards and SAST, prevents the dynamic generation or inclusion of attacker-supplied code.

none

Controls that restrict unauthorized or malicious code from being introduced via external networks or removable media limit opportunities for an attacker to inject and execute arbitrary code.

References