CVE-2025-23871
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 Bas Matthee LSD Google Maps Embedder lsd-google-maps-embedder allows Cross Site Request Forgery.This issue affects LSD Google Maps Embedder: 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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the WordPress plugin 'LSD Google Maps Embedder' versions 1.1 and below allows attackers to trick authenticated administrators into performing unintended actions (such as modifying plugin settings or injecting malicious content) by exploiting the lack of anti-CSRF token validation in the plugin's forms and AJAX 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
- 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 installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate 'LSD Google Maps Embedder' to read the version number. Alternatively, open the main plugin PHP file in wp-content/plugins/lsd-google-maps-embedder/ and check the 'Version:' header comment.Affected if The installed version is 1.1 or lower
-
Search plugin files for nonce validation functionsUse a file search or grep tool to scan all PHP files in the plugin directory (wp-content/plugins/lsd-google-maps-embedder/) for the presence of WordPress nonce functions: wp_nonce_field, wp_nonce_url, check_admin_referer, or wp_verify_nonce.Affected if None of these nonce validation functions are found anywhere in the plugin code
-
Inspect AJAX handlers for nonce verificationSearch the plugin for 'add_action' calls containing 'wp_ajax_' to locate AJAX endpoints. Open each identified AJAX handler file and verify whether check_admin_referer or wp_verify_nonce is called before any processing logic executes.Affected if AJAX endpoints exist but do not call any nonce verification functions before processing requests
-
Review admin form submissions for nonce fieldsSearch PHP files for HTML form tags (<form). For each form found, verify that wp_nonce_field is called to generate a hidden nonce field, or that the form action URL includes a nonce via wp_nonce_url.Affected if Forms submit data to the server without including or verifying a nonce token
You are affected if the installed plugin version is 1.1 or below AND the plugin lacks WordPress nonce validation in its forms or AJAX handlers.
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 (anti-CSRF tokens) in all forms and AJAX actions within the plugin to verify the origin and intent of requests; verify the nonce validity before processing any state-changing operations.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23871 — 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-23871 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