CVE-2020-11700 json
An issue was discovered in Titan SpamTitan 7.07.
published 6y ago modified 4mo ago also EUVD-2020-4042
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.1%
- EPSS 7.1% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB
Summary
An issue was discovered in Titan SpamTitan 7.07. Improper sanitization of the parameter fname, used on the page certs-x.php, would allow an attacker to retrieve the contents of arbitrary files. The user has to be authenticated before interacting with this page.
Is CVE-2020-11700 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 FencerTimeline
- Published
- First public exploit (EDB-48817)
Exploit prediction
7.09% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-48817 SpamTitan 7.07 - Remote Code Execution (Authenticated) webapps, 2020-09-18
- sensepost.com https://sensepost.com/blog/2020/clash-of-the-spamtitan/ referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/159218/SpamTitan-7.07-Remote-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
sensepost.com
/blog/2020/clash-of-the-spamtitan/
exploit, third-party-advisory
-
packetstormsecurity.com
/files/159218/SpamTitan-7.07-Remote-Code-Execution.html
exploit, third-party-advisory
-
spamtitan.com
/
vendor-advisory
-
github.com
/felmoltor
third-party-advisory
-
twitter.com
/felmoltor
third-party-advisory
Sources
- CVE List CVE-2020-11700
- NVD CVE-2020-11700
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.