CVE-2025-23513
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 jd7777 Bible Embed bible-embed allows Stored XSS.This issue affects Bible Embed: from n/a through <= 0.0.4.
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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the Bible Embed WordPress plugin enables attackers to trick authenticated administrators into performing unintended actions that result in Stored XSS. The lack of anti-CSRF tokens on state-changing operations allows malicious script injection that persists 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.
-
Identify if Bible Embed plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and search for 'Bible Embed' or 'bible-embed'Affected if The plugin is present in the WordPress installation
-
Check installed Bible Embed plugin versionIn Plugins list, click 'View Details' under Bible Embed to display the version number, or check the plugin header in /wp-content/plugins/bible-embed/bible-embed.phpAffected if Version cannot be verified against a fixed patch version due to lack of disclosed version range; assume affected if plugin is installed
-
Inspect plugin forms for nonce presenceExamine all state-changing forms in the plugin (plugin settings, save options, any admin action forms) by reviewing PHP source files in /wp-content/plugins/bible-embed/ and check if wp_nonce_field() or wp_nonce_url() is usedAffected if Any form handling admin actions lacks WordPress nonce verification tokens
-
Inspect AJAX actions for nonce verificationReview plugin AJAX handlers (admin-ajax.php calls) in the plugin files and verify if 'check_ajax_referer' or 'wp_verify_nonce' is called before processing requestsAffected if AJAX actions process requests without verifying nonce tokens
-
Check if stored XSS is possible via plugin input handlingTest by submitting HTML/script tags in plugin settings fields (if accessible) and verify if data is stored and later displayed without proper sanitization (esc_html, esc_attr, etc.)Affected if Plugin saves user input to database and displays it without sanitization on admin or public pages
Environment is affected if Bible Embed plugin is installed and any state-changing operation (forms or AJAX) processes requests without WordPress nonce verification, potentially allowing stored XSS via CSRF-tricked 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.
From vendor dataImplement WordPress nonces on all form submissions and AJAX actions, and ensure all user-supplied data is properly sanitized on output to prevent stored XSS execution.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23513 — 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-23513 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