WP Security CheckVulnerability data as of November 8, 2026

Vulnerability alerts / November 7, 2026

Vulnerability in Stop Spammers Classic — CVE-2026-120477

MediumSeverity
CVSS 4.7
0.3%Estimated exploit probability
EPSS
30,000+ sitesInstalls
2026.7Fixed in

What to do now

Update Stop Spammers Classic to 2026.7 or later.

Affected versions

  • Everything up to and including 2026.6

Affected: Stop Spammers Classic (plugin, stop-spammer-registrations-plugin)

Check: The plugin on wordpress.org / Our record for Stop Spammers Classic

What the vulnerability is

The Stop Spammers Classic plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'author' POST parameter in versions up to, and including, 2026.6. An unauthenticated POST handled on init stores the attacker-supplied author field (after sanitize_text_field, which does not escape single quotes) into the ss_stop_sp_reg_stats option history. The Log Report admin page then renders that stored value inside a single-quoted JavaScript string within a double-quoted onclick attribute using esc_js(); because esc_js() uses _wp_specialchars with ENT_COMPAT it does not escape single quotes, allowing the stored value to break out of the JS string literal and inject arbitrary JavaScript. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute whenever an administrator with manage_options access clicks the 'Report to SFS' link on an attacker-poisoned log row (the StopForumSpam API key must be configured for that link to be rendered — the field is empty by default). Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.

This description is reproduced verbatim from the public vulnerability record.

Sources

See other alerts