Skip to content
Fencer Intel
critical 9.8

CVE-2020-11698 in the critical feed json

An issue was discovered in Titan SpamTitan 7.07.

published 6y ago modified 4mo ago also EUVD-2020-4040

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
73.2%
EPSS 73.2% chance of exploitation in 30 days, percentile 99.4%
public exploits
2
Metasploit and Exploit-DB

Summary

An issue was discovered in Titan SpamTitan 7.07. Improper input sanitization of the parameter community on the page snmp-x.php would allow a remote attacker to inject commands into the file snmpd.conf that would allow executing commands on the target server.

Is CVE-2020-11698 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 Fencer

Timeline

  1. First public exploit (Metasploit exploit/freebsd/webapp/spamtitan_unauth_rce)
  2. Published

Exploit prediction

73.20% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Metasploit exploit/freebsd/webapp/spamtitan_unauth_rce SpamTitan Unauthenticated RCE metasploit exploit, normal rank, 2020-04-17
  • EDB-48856 SpamTitan 7.07 - Unauthenticated Remote Code Execution webapps, 2020-10-05
  • 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/159470/SpamTitan-7.07-Remote-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/160809/SpamTitan-7.07-Command-Injection.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-77 Improper Neutralization of Special Elements used in a Command

References

Sources

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.