CVE-2017-20096: A vulnerability classified as problematic has been found in WP-SpamFree Anti-Spam Plugin 2.1.1.4

Routine

LOW 3.5DOWNGRADE

CVE-2017-20096 is a low-severity flaw (CVSS 3.5) affecting wp-spamfree anti-spam. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability classified as problematic has been found in WP-SpamFree Anti-Spam Plugin 2.1.1.4. This affects an unknown part. The manipulation leads to basic cross site scripting. It is possible to initiate the attack remotely.

Why this priority

Public exploit reference

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

Risk facts

CVSS score	3.5 (Low)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.6% (top 49%)
CISA exploited list	No
Weakness	CWE-80, CWE-79
Published	2022-06-24
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: wp-spamfree anti-spam project

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

Am I affected?

Timeline

2022-06-24 07:15 UTCPublished CVE record published
2026-06-17 01:15 UTCUpdated Record last modified

wp-spamfree anti-spam project wp-spamfree anti-spam DOWNGRADE

Affected: 2.1.1.4

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.1.1.4

1. Check installed version

apt-cache policy wp-spamfree-anti-spam || rpm -q wp-spamfree-anti-spam || wp-spamfree-anti-spam --version

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

apt-cache madison wp-spamfree-anti-spam sudo apt install wp-spamfree-anti-spam=<VERSION_BEFORE_2.1.1.4> sudo apt-mark hold wp-spamfree-anti-spam

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

dnf --showduplicates list wp-spamfree-anti-spam sudo dnf downgrade wp-spamfree-anti-spam-<VERSION_BEFORE_2.1.1.4> sudo dnf versionlock add wp-spamfree-anti-spam

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.

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-2017-20096?

wp-spamfree anti-spam: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-20096 being exploited?

CVE-2017-20096 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-2017-20096 affect?

CVE-2017-20096 affects wp-spamfree anti-spam. Severity is low (CVSS 3.5). A vulnerability classified as problematic has been found in WP-SpamFree Anti-Spam Plugin 2.1.1.4. This affects an unknown part. The manipulation leads to basic cross site scripting. It is possible to initiate the attack remotely.

How urgent is CVE-2017-20096?

Priority 30/100. Public exploit reference

References

← Back to latest CVEs