CVE-2014-7237 json
lib/TWiki/Sandbox.pm in TWiki 6.0.0 and earlier, when running on Windows, allows remote attackers to bypass intended access restrictions an…
published 12y ago modified 4mo ago also EUVD-2014-7108
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 20.1%
- EPSS 20.1% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
lib/TWiki/Sandbox.pm in TWiki 6.0.0 and earlier, when running on Windows, allows remote attackers to bypass intended access restrictions and upload files with restricted names via a null byte (%00) in a filename to bin/upload.cgi, as demonstrated using .htaccess to execute arbitrary code.
Is CVE-2014-7237 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 FencerExploit prediction
20.06% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- twiki.org http://twiki.org/cgi-bin/view/Codev/SecurityAlert-CVE-2014-7237 referenced PoC, tagged "exploit" by a source, unverified
- securitytracker.com http://www.securitytracker.com/id/1030982 referenced PoC, tagged "exploit" by a source, unverified
- seclists.org http://seclists.org/fulldisclosure/2014/Oct/45 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
twiki.org
/cgi-bin/view/Codev/SecurityAlert-CVE-2014-7237
exploit
-
securitytracker.com
/id/1030982
vdb-entry, exploit
-
seclists.org
/fulldisclosure/2014/Oct/45
mailing-list, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/96952
vdb-entry
Sources
- CVE List CVE-2014-7237
- NVD CVE-2014-7237
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.