Security readout for executives and security teams
Plain-English summary
This issue lets a WordPress administrator upload files that the WPvivid plugin should have rejected. On NGINX-hosted sites, those files may be reachable from the web, which can make server takeover possible. The attacker needs Administrator-level access first, so this is most urgent where admin accounts are shared, weakly protected, or compromised.
Executive priority
Treat this as a high-priority plugin update for WordPress estates, especially NGINX-hosted sites. It is not an unauthenticated internet-wide bug, but compromised or misused admin access could turn it into server-level impact.
Technical view
WPvivid Backup & Migration versions up to and including 0.9.112 lack file type validation in the upload_files/wpvivid_upload_file path. The CVSS 3.1 score is 7.2 with high confidentiality, integrity, and availability impact. Sources note uploaded files are web-accessible on NGINX, while an .htaccess file blocks access on Apache in the target folder.
Likely exposure
Exposure is limited to WordPress sites running WPvivid Backup & Migration at 0.9.112 or earlier. Practical impact is higher on NGINX because uploaded files may be externally accessible. Apache deployments have a documented .htaccess protection in the target upload folder, but should still update and validate configuration.
Exploitation context
No CISA KEV listing is provided, and the bundle does not establish active exploitation. Public research and a GitHub reference exist, so defenders should assume the issue is knowable. The required Administrator-level access materially raises the attack bar but does not remove risk after credential compromise.
Researcher notes
The core weakness is CWE-434 arbitrary file upload from missing file type validation. The key environmental qualifier is web server behavior: NGINX increases reachability of uploaded files, while Apache has an .htaccess barrier in the target folder according to the CVE description.
Mitigation direction
- Update WPvivid Backup & Migration beyond version 0.9.112 when available from the vendor.
- Review vendor and WordPress plugin guidance for the fixed release and upgrade notes.
- Restrict WordPress Administrator access to named, necessary users only.
- Require MFA and strong credential hygiene for all Administrator accounts.
- For NGINX sites, verify upload directories cannot execute or expose unsafe files.
Validation and detection
- Inventory all WordPress sites using WPvivid Backup & Migration.
- Confirm installed WPvivid versions are newer than 0.9.112.
- Identify whether affected sites run NGINX, Apache, or mixed proxy configurations.
- Review WPvivid upload and backup directories for unexpected executable files.
- Audit recent Administrator activity around plugin file uploads and backups.
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-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection 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-13869 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
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/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:H/UI:N/S:U/C:H/I:H/A:H1.25.9WordfenceVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:H/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
Vendor Notified
- 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/0082e46d-fdbe-4ab7-bba3-0681a25d4495?source=cveCVE reference, Wordfence
- https://plugins.trac.wordpress.org/changeset/3242904/wpvivid-backuprestoreCVE reference, Wordfence
- https://github.com/d0n601/CVE-2024-13869CVE reference, Wordfence
- https://ryankozak.com/posts/cve-2024-13869/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.
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.