dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2025-69151

HIGH · 7.1 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Unauthenticated Cross Site Scripting (XSS) in Grand Car Rental <= 3.7 versions.

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 confidence

Grand Car Rental plugin versions 3.7 and below contains an unauthenticated cross-site scripting (XSS) vulnerability. Attackers can inject malicious JavaScript through a vulnerable input parameter without requiring any authentication, potentially allowing session hijacking, cookie theft, or user redirection.

MitigationUpdate Grand Car Rental to a version newer than 3.7. If no update is available, implement output encoding and input validation on all user-supplied parameters, or disable the plugin until a patch is released.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Grand Car Rental plugin is installed
    Access your WordPress admin dashboard, navigate to Plugins, and confirm Grand Car Rental appears in the list of installed plugins. Alternatively, check the wp-content/plugins/ directory for a folder named 'grand-car-rental' or similar.
    Affected if The plugin is present in the WordPress installation
  2. Check the installed plugin version
    In the WordPress admin Plugins page, locate Grand Car Rental and view the version number displayed under the plugin name. Alternatively, open the main plugin file (usually grand-car-rental.php) and look for the version comment or defined constant.
    Affected if The version is 3.7 or any version lower than 3.7
  3. Confirm the plugin is active and accessible
    In the WordPress admin Plugins page, verify that Grand Car Rental shows as 'Active'. Also confirm the frontend car rental forms or pages are publicly accessible without login.
    Affected if The plugin is active and its car rental forms are publicly accessible without authentication
  4. Identify the vulnerable input parameter exposure
    Review your WordPress pages that contain Grand Car Rental booking forms. Check the source code or use a browser developer tool to identify which form parameters (such as pickup location, drop-off location, name, email, or vehicle selection) are submitted to the plugin's handling scripts. The CVE indicates unauthenticated users can inject script through one of these parameters.
    Affected if Public-facing forms accept user input without sanitization and the plugin is unpatched (version 3.7 or below)

Your environment is affected if the Grand Car Rental plugin is installed at version 3.7 or below and its booking forms are publicly accessible to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Grand Car Rental to a version newer than 3.7. If no update is available, implement output encoding and input validation on all user-supplied parameters, or disable the plugin until a patch is released.

Recommended fix Moderate confidence

Any version above 3.7 (latest available version recommended)

  1. 1. Verify the current version of Grand Car Rental plugin/theme installed on the WordPress site
  2. 2. Backup the WordPress database and files before making any changes
  3. 3. Update Grand Car Rental to the latest available version from the official WordPress repository or vendor
  4. 4. If automatic updates are enabled, verify the update completed successfully
  5. 5. Clear any site caches after the update
  6. 6. Test the affected functionalities to confirm the vulnerability is remediated
Caveat Review changelog for any breaking changes between current and new version before updating

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-69151 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-69151 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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