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

CVE-2026-13015

MEDIUM · 6.1 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 7 weeks old

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
The Wp Google Places Review Slider plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'place' parameter in versions up to, and including, 18.1. This is due to insufficient input sanitization and output escaping in admin/partials/googlecrawl_dfs.php, where the $_GET['place'] value is URL-decoded, stripslashes()'d, and echoed directly into an HTML value attribute with no esc_attr() call when the supplied place is not already a stored key in the wprev_google_crawls option. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a specially crafted link.

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 · high confidence

The Wp Google Places Review Slider plugin for WordPress (versions up to 18.1) contains a reflected XSS vulnerability in admin/partials/googlecrawl_dfs.php. The 'place' GET parameter is URL-decoded, has stripslashes() applied, and is echoed directly into an HTML value attribute without sanitization via esc_attr(), allowing arbitrary JavaScript injection when the place value is not a pre-existing key in the wprev_google_crawls option.

MitigationApply esc_attr() around the echoed $_GET['place'] value in the vulnerable file, validate that the place parameter corresponds to a stored key before rendering, and update to version 18.2 or later when available.

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
None

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

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 the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and find 'Wp Google Places Review Slider' or check the plugin files for version information in the main PHP file header
    Affected if Plugin version is 18.1 or earlier (version 18.2 and later are patched)
  2. Confirm the vulnerable file exists
    Check for the existence of wp-content/plugins/wp-google-places-review-slider/admin/partials/googlecrawl_dfs.php
    Affected if The file exists and contains an echo statement using the 'place' GET parameter without esc_attr()
  3. Examine the wprev_google_crawls option
    Access WordPress database or use wp-cli: wp option get wprev_google_crawls. If using MySQL directly: SELECT option_value FROM wp_options WHERE option_name = 'wprev_google_crawls';
    Affected if The option contains stored place keys; the XSS only triggers when the 'place' GET parameter is NOT a key in this option
  4. Test the vulnerable parameter
    Send a GET request to the affected page with a test value for 'place' that is not in the wprev_google_crawls keys, for example: /wp-admin/admin.php?page=googlecrawl_dfs&place=<script>alert(1)</script>
    Affected if The response reflects the unsanitized place value in an HTML attribute without escaping

You are affected if the Wp Google Places Review Slider plugin version is 18.1 or earlier AND the vulnerable file exists AND the 'place' parameter can be reflected without sanitization when the value is not a stored key in the wprev_google_crawls option.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply esc_attr() around the echoed $_GET['place'] value in the vulnerable file, validate that the place parameter corresponds to a stored key before rendering, and update to version 18.2 or later when available.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13015 — 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-2026-13015 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