Security readout for executives and security teams
Plain-English summary
CVE-2024-11635 is a critical unauthenticated remote code execution issue in the WordPress File Upload plugin up to and including 4.24.12. A public website running an affected version could let an outside attacker run code on the server. Treat exposed WordPress sites using this plugin as urgent until verified remediated.
Executive priority
Immediate priority for any public WordPress site using this plugin. The business risk is server compromise without login, which can lead to data theft, defacement, malware placement, or service disruption. Assign same-day owner action for inventory and remediation.
Technical view
The vulnerability is described as CWE-94 code injection through the plugin's wfu_ABSPATH cookie parameter. The CVSS 3.1 score is 9.8 because exploitation is network-accessible, low complexity, requires no privileges or user interaction, and can impact confidentiality, integrity, and availability.
Likely exposure
Likely exposure is WordPress installations using the WordPress File Upload plugin version 4.24.12 or earlier, especially internet-facing sites. The bundle's affected-product metadata appears inconsistent, so confirm by plugin slug, installed version, and vendor advisory rather than relying only on CPE data.
Exploitation context
The source bundle includes public technical references, but KEV is false and no cited source in the bundle confirms active exploitation. Do not assume exploitation in the wild without additional evidence. The issue is still high urgency because unauthenticated RCE on WordPress commonly creates broad operational risk.
Researcher notes
Evidence supports unauthenticated RCE via a cookie-controlled path parameter and CWE-94 classification. The bundle does not prove active exploitation and has inconsistent affected-product metadata. Keep analysis tied to the WordPress File Upload plugin, version threshold, and vendor/Wordfence references.
Mitigation direction
- Inventory WordPress sites for the WordPress File Upload plugin and installed versions.
- Upgrade to a vendor-confirmed fixed version if available.
- If no confirmed fix is available, disable or remove the plugin pending vendor guidance.
- Review web server and WordPress logs for suspicious requests involving the plugin.
- Prioritize backups and recovery readiness for affected WordPress hosts.
Validation and detection
- Confirm whether the plugin version is 4.24.12 or earlier.
- Check vendor and Wordfence guidance for fixed-version details.
- Verify the plugin is disabled, removed, or updated on production sites.
- Review recent access logs for abnormal plugin downloader or cookie activity.
- Confirm file integrity and unexpected code changes on affected hosts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-11635 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9WordfenceVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineWordfence
Disclosed
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/b5165f60-6515-4a2c-a124-cc88155eaf01?source=cveCVE reference, Wordfence
- https://plugins.svn.wordpress.org/wp-file-upload/trunk/wfu_file_downloader.phpCVE reference, Wordfence
- https://abrahack.com/posts/wp-file-upload-rce-part1/CVE reference, Wordfence
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.