CVE-2013-5917: SQL injection vulnerability in wp-comments-post.php in the NOSpam PTI plugin 2.1 for WordPress allows remote a

This month

HIGH 7.5DOWNGRADE

CVE-2013-5917 is a high-severity flaw (CVSS 7.5) affecting nospam pti. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

SQL injection vulnerability in wp-comments-post.php in the NOSpam PTI plugin 2.1 for WordPress allows remote attackers to execute arbitrary SQL commands via the comment_post_ID parameter.

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	2.8% (top 14%)
CISA exploited list	No
Weakness	CWE-89
Published	2013-09-23
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: rodrigo coimbra

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2013-09-23 10:18 UTCPublished CVE record published
2026-06-16 23:59 UTCUpdated Record last modified

rodrigo coimbra nospam pti DOWNGRADE

Affected: 2.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.1

1. Check installed version

apt-cache policy nospam-pti || rpm -q nospam-pti || nospam-pti --version

2. No fixed release: DOWNGRADE to a release before 2.1 (Debian / Ubuntu)

apt-cache madison nospam-pti sudo apt install nospam-pti=<VERSION_BEFORE_2.1> sudo apt-mark hold nospam-pti

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list nospam-pti sudo dnf downgrade nospam-pti-<VERSION_BEFORE_2.1> sudo dnf versionlock add nospam-pti

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: WordPress Plugin NOSpamPTI - Blind SQL Injection

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2013-5917?

nospam pti: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2013-5917 being exploited?

CVE-2013-5917 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2013-5917 affect?

CVE-2013-5917 affects nospam pti. Severity is high (CVSS 7.5). SQL injection vulnerability in wp-comments-post.php in the NOSpam PTI plugin 2.1 for WordPress allows remote attackers to execute arbitrary SQL commands via the comment_post_ID parameter.

How urgent is CVE-2013-5917?

Priority 53/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities · PHP vulnerabilities

References

← Back to latest CVEs