CVE-2024-12219
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Stop Registration Spam plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.23. This is due to missing or incorrect nonce validation. This makes it possible for unauthenticated attackers to inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE-2024-56017 is likely a duplicate of this issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Stop Registration Spam WordPress plugin up to version 1.23 is vulnerable to Cross-Site Request Forgery due to missing or incorrect nonce validation. This allows unauthenticated attackers to forge administrative actions by tricking site admins into clicking malicious links, potentially enabling stored XSS injection through the forged requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the Stop Registration Spam plugin filesNavigate to wp-content/plugins/ in your WordPress installation and confirm the presence of a folder named 'stop-registration-spam' or similar variant. Use 'ls' or file explorer to verify the directory exists.Affected if The plugin directory is present on the server
-
Identify the installed plugin versionOpen the plugin's main PHP file (often stop-registration-spam.php) or the readme.txt file in the plugin folder and locate the 'Version:' field in the plugin header comment block. Alternatively, run 'wp plugin list --name="stop-registration-spam"' if WP-CLI is available.Affected if The version listed is 1.23 or lower, or no version is detectable (older installation)
-
Confirm the plugin is activeLog in to the WordPress admin dashboard and go to Plugins > Installed Plugins. Verify whether the Stop Registration Spam plugin is currently activated. Alternatively, query the wp_options table for the active_plugins option.Affected if The plugin appears in the active plugins list and is toggled on
Your environment is affected if the Stop Registration Spam plugin is installed, active, and the version is 1.23 or earlier, as these versions lack proper nonce validation and are vulnerable to CSRF attacks that could inject stored XSS.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate the plugin to version 1.24 or later once the patch is available. Until then, enforce admin awareness about clicking untrusted links and consider disabling the plugin if not essential.
Version 1.24 or latest available version
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate the 'Stop Registration Spam' plugin
- Check the current version number
- Update the plugin to the latest available version (1.24 or higher)
- Verify the update was successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12219 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-12219 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data