CVE-2024-12634
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 Related Posts, Inline Related Posts, Contextual Related Posts, Related Content By PickPlugins plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including 2.0.59. This is due to missing nonce validation on a function. 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.
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 PickPlugins Related Posts WordPress plugin versions up to 2.0.59 lacks nonce validation on a specific function, allowing unauthenticated attackers to forge requests that trick administrators into executing malicious actions. Successful exploitation enables injection of malicious web scripts (XSS) via CSRF, as the attacker relies on social engineering to get a logged-in admin to click a crafted link.
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.
-
Verify PickPlugins Related Posts plugin is installedNavigate to WordPress admin > Plugins and locate 'PickPlugins Related Posts' in the installed plugins list, or check the filesystem at /wp-content/plugins/pickplugins-related-posts/ for the plugin directoryAffected if The plugin is installed and active in WordPress
-
Determine the installed plugin versionIn WordPress admin > Plugins page, find PickPlugins Related Posts and read the version number displayed beneath the plugin name, or open the plugin's main PHP file and look for the Version header in the plugin comment block, or check the readme.txt fileAffected if Version cannot be determined or is 2.0.59 or lower
-
Compare version against affected rangeThe vulnerability affects all versions up to and including 2.0.59. If your installed version is 2.0.60 or later, the nonce validation fix has been appliedAffected if Installed version is 2.0.59 or lower, or the version is unknown
Your environment is affected if the PickPlugins Related Posts plugin is installed with version 2.0.59 or lower, allowing unauthenticated attackers to exploit missing nonce validation via social engineering of administrators.
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 the latest version once available; the fix requires implementing proper nonce validation on the affected function(s) to verify request origin and intent.
Version 2.0.60 or later (upgrade from 2.0.59 or below)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the 'Related Posts, Inline Related Posts, Contextual Related Posts, Related Content By PickPlugins' plugin
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. Verify the update was successful by checking the plugin version after updating
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12634 — 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-12634 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