CVE-2026-12513 json
Shared Files < 1.7.68 - Unauthenticated Arbitrary File Deletion via Path Traversal
published 2mo ago modified 2mo ago also EUVD-2026-67565
- cvss
- 6.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
The Shared Files WordPress plugin before 1.7.67, shared-files-pro WordPress plugin before 1.7.68 do not properly sanitize a file path taken from a frontend file submission and their single-pass traversal filter is bypassable, allowing unauthenticated users to store a path that points outside the uploads directory. When the corresponding file entry is later permanently deleted, an arbitrary file on the server (such as wp-config.php) is deleted, leading to denial of service and potential site takeover.
Patch / fix
- Unknown Shared Files 1.7.67
- Unknown shared-files-pro 1.7.68
Is CVE-2026-12513 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/25c9fa21-c48b-4333-8abc-87230dc4c869/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H |
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H |
Affected products
- Unknown Shared Files
- Unknown shared-files-pro
Classification
- Weakness
-
- CWE-73 External Control of File Name or Path
- Technology feeds
References
-
wpscan.com
/vulnerability/25c9fa21-c48b-4333-8abc-87230dc4c869/
exploit, vdb-entry, technical-description
Sources
- CVE List CVE-2026-12513
- NVD CVE-2026-12513
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.