GHSA-XVC3-WFF6-474C
Vulnerability from github – Published: 2026-11-07 06:31 – Updated: 2026-11-07 06:31The 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.
{
"affected": [],
"aliases": [
"CVE-2026-120477"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-07T05:18:11Z",
"severity": "MODERATE"
},
"details": "The Stop Spammers Classic plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the \u0027author\u0027 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 \u0027Report to SFS\u0027 link on an attacker-poisoned log row (the StopForumSpam API key must be configured for that link to be rendered \u2014 the field is empty by default). Successful exploitation additionally requires an action by an administrator \u2014 the attacker cannot trigger the vulnerability on their own.",
"id": "GHSA-xvc3-wff6-474c",
"modified": "2026-11-07T06:31:15Z",
"published": "2026-11-07T06:31:14Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-120477"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/stop-spammer-registrations-plugin/trunk/classes/ss_log_bad.php#L63"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/stop-spammer-registrations-plugin/trunk/settings/ss_reports.php#L165"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/stop-spammer-registrations-plugin/trunk/stop-spammer-registrations-new.php#L323"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/stop-spammer-registrations-plugin/trunk/stop-spammer-registrations-new.php#L600"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset?reponame=\u0026old=3784211%40stop-spammer-registrations-plugin\u0026new=3784211%40stop-spammer-registrations-plugin"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/29fe0bc9-b460-4158-86fc-ad2980cc827a?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.