Security readout for executives and security teams
Plain-English summary
A WordPress plugin used to embed Google Maps can be abused through a forged request that may plant stored script content. The business risk is website compromise impact from affected plugin installations, not broad platform compromise. The source bundle names LSD Google Maps Embedder versions through 1.1 only.
Executive priority
Prioritize this as a high-risk WordPress plugin exposure when the plugin is present. If the plugin is absent, no action is indicated beyond monitoring.
Technical view
CVE-2025-23871 is a CWE-352 CSRF issue in Bas Matthee LSD Google Maps Embedder, package lsd-google-maps-embedder, reported as CSRF to stored XSS. It affects versions through 1.1. CVSS 3.1 is 7.1 with network attack vector, low complexity, required user interaction, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely limited to WordPress sites with LSD Google Maps Embedder installed at version 1.1 or earlier. The provided sources do not identify affected CPEs or other products.
Exploitation context
The bundle does not show CISA KEV listing or other evidence of active exploitation. The CVSS vector indicates remote reachability and required user interaction. No exploit details are needed to understand exposure.
Researcher notes
Evidence is narrow: CVE metadata and Patchstack identify CSRF leading to stored XSS, but the bundle does not include proof-of-concept details, exploitation confirmation, or a named fixed version.
Mitigation direction
- Inventory WordPress sites for lsd-google-maps-embedder version 1.1 or earlier.
- Disable or remove the plugin if it is not business-critical.
- Check Patchstack and vendor guidance for a confirmed fixed version.
- Apply any confirmed vendor patch after normal testing.
- Review affected sites for unexpected stored script content.
Validation and detection
- Confirm whether the plugin slug lsd-google-maps-embedder is installed.
- Record installed plugin version and compare it with <= 1.1.
- Check public pages using map embeds for unexpected script behavior.
- Review WordPress admin content changes around the exposure window.
- Track CVE and Patchstack entries for remediation updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-23871 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.