CVE-2016-7982 in the critical feed json
Directory traversal vulnerability in ecrire/exec/valider_xml.php in SPIP 3.1.2 and earlier allows remote attackers to enumerate the files o…
published 2017-01-18 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-8830
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 20.5%
- EPSS 20.5% chance of exploitation in 30 days, percentile 97%
- public exploits
- 1
- Exploit-DB
Summary
Directory traversal vulnerability in ecrire/exec/valider_xml.php in SPIP 3.1.2 and earlier allows remote attackers to enumerate the files on the system via the var_url parameter in a valider_xml action.
Patch / fix
- spip Debian 14, Debian 13 3.1.3-1
debian advisories DEBIAN-CVE-2016-7982
Timeline
- First public exploit (EDB-40596)
- Published
Exploit prediction
20.52% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-40596 SPIP 3.1.1/3.1.2 - File Enumeration / Path Traversal webapps, 2016-10-20
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
core.spip.net
/projects/spip/repository/revisions/23200
issue-tracking, patch, vendor-advisory
-
openwall.com
/lists/oss-security/2016/10/06/6
mailing-list, patch, third-party-advisory
-
securityfocus.com
/bid/93451
vdb-entry, third-party-advisory
-
openwall.com
/lists/oss-security/2016/10/05/17
mailing-list, third-party-advisory
- sysdream.com /news/lab/2016-10-19-spip-3-1-1-3-1-2-file-enumeration-path-traversal-cve-2016-7982/
-
openwall.com
/lists/oss-security/2016/10/12/8
mailing-list, third-party-advisory
Sources
- CVE List CVE-2016-7982
- NVD CVE-2016-7982
Fencer Vulns 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.