CVE-2025-23476
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in isnowfy my-related-posts my-related-posts allows Stored XSS.This issue affects my-related-posts: from n/a through <= 1.1.
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 confidenceCSRF vulnerability in the my-related-posts WordPress plugin (versions <= 1.1) allows attackers to inject malicious JavaScript via stored XSS by tricking authenticated administrators into submitting crafted requests. The lack of CSRF token validation on form submissions enables attackers to silently inject payloads that persist in the database.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
-
Check if my-related-posts plugin is installedAccess WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'my-related-posts' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'my-related-posts' or similar.Affected if Plugin is not found in the installed plugins list, then not affected
-
Identify the installed version of my-related-postsIn the WordPress admin plugins list, click on the plugin to view its details, or check the main plugin PHP file header for the 'Version' field. Common path: /wp-content/plugins/my-related-posts/my-related-posts.phpAffected if Version number displayed is 1.1 or lower, indicating the vulnerable version is installed
-
Verify the plugin admin interface is accessibleLog into the WordPress admin panel and navigate to the plugin settings page (usually under Settings or a dedicated menu item named after the plugin). Check if admin pages load without errors.Affected if Plugin settings page loads successfully and displays form interfaces, meaning the attack surface is present
-
Inspect plugin PHP files for missing nonce verificationExamine the main plugin PHP file for form handling code. Look for AJAX actions or form submission handlers. Search for presence of 'wp_verify_nonce' or 'check_admin_referer' functions in the code that handles form data. Use grep or a code editor to search for these nonce verification functions.Affected if Form processing code exists but does not contain wp_verify_nonce or check_admin_referer calls before processing submitted data, confirming the CSRF vulnerability is present
User is affected if the my-related-posts plugin is installed with version 1.1 or lower and the plugin admin interface with unprotected forms is accessible.
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.
From vendor dataImplement anti-CSRF tokens (nonces) on all data-modifying forms and AJAX actions, and validate these tokens on the server side before processing any request.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23476 — 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-2025-23476 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