LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31613: WordPress AB Google Map Travel plugin <= 4.6 - CSRF to Stored XSS vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in Aboobacker. AB Google Map Travel ab-google-map-travel allows Cross Site Request Forgery.This issue affects AB Google Map Travel : from n/a through <= 4.6.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE affects the WordPress AB Google Map Travel plugin through version 4.6. A successful CSRF attack could cause stored cross-site scripting, meaning malicious script content may persist in the site and affect visitors or administrators. The sources do not identify active exploitation or a fixed version.

Executive priority

Treat this as high priority for any WordPress property using this plugin. Stored XSS can affect trust, user sessions, and site integrity, but urgency depends on whether the plugin is installed and exposed. No active exploitation is documented in the supplied sources.

Technical view

CVE-2025-31613 is a CWE-352 CSRF issue in ab-google-map-travel through 4.6, described as CSRF to stored XSS. CVSS 3.1 is 7.1 with network attack vector, low complexity, no attacker privileges, required user interaction, and changed scope.

Likely exposure

Exposure is likely limited to WordPress sites that have AB Google Map Travel installed at version 4.6 or earlier. The provided sources do not define vulnerable endpoints, required victim role, or installed-base prevalence.

Exploitation context

The CVSS vector indicates remote exploitation with user interaction required. CISA KEV status is false in the bundle, and no cited source states active exploitation. Because this is CSRF to stored XSS, exploitation likely depends on tricking a legitimate user into an unsafe action.

Researcher notes

The public bundle is sparse. It confirms CSRF affecting AB Google Map Travel through 4.6 and labels the outcome as stored XSS, but does not provide endpoint details, proof-of-concept information, exploit telemetry, or a patched version. Avoid asserting more than the sources support.

Mitigation direction

  • Inventory WordPress sites for the AB Google Map Travel plugin.
  • If version is <=4.6, disable or remove it until vendor guidance confirms safety.
  • Monitor the CVE record and Patchstack entry for fixed-version details.
  • Restrict administrative access to trusted users and hardened sessions.
  • Review stored map or plugin content for unexpected script changes.

Validation and detection

  • Check WordPress plugin inventories for slug ab-google-map-travel.
  • Record installed versions and flag any version <=4.6.
  • Review Patchstack and CVE records for current remediation guidance.
  • Inspect plugin-managed content for unauthorized stored script content.
  • Confirm no public claim of active exploitation before reporting exploitation status.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
cve · low confidence lookup

CVE-2025-31613 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2025-31613Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Aboobacker.AB Google Map Travelab-google-map-travel, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

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.