dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-30783

HIGH · 8.2 CVSS v3.1 Published 2025-03-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/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
Cross-Site Request Forgery (CSRF) vulnerability in jgwhite33 WP Google Review Slider wp-google-places-review-slider allows SQL Injection.This issue affects WP Google Review Slider: from n/a through <= 16.0.

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

Cross-Site Request Forgery (CSRF) vulnerability in the WP Google Review Slider plugin (wp-google-places-review-slider) enables SQL Injection through forged requests. The vulnerability exists in versions up to and including 16.0, allowing attackers to execute arbitrary SQL queries via crafted requests when combined with CSRF exploitation.

MitigationUpdate WP Google Review Slider to a version beyond 16.0. Implement anti-CSRF tokens on all state-changing actions and use prepared statements/parameterized queries to prevent SQL injection.

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
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/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. Locate the WP Google Review Slider plugin files
    Check if the plugin directory wp-content/plugins/wp-google-places-review-slider/ exists on the WordPress server
    Affected if The plugin directory exists and the plugin is installed
  2. Determine the installed plugin version
    Open the main plugin file (wp-google-places-review-slider.php) and locate the Version header in the plugin comment block, or check readme.txt for the version field
    Affected if The version number is 16.0 or lower
  3. Verify the plugin is active
    Log into WordPress admin and check Plugins > Installed Plugins to confirm WP Google Review Slider is activated
    Affected if The plugin is active and accessible to authenticated users
  4. Inspect form actions for CSRF protection
    Examine the plugin's admin forms (in the /admin/ folder if present) and look for nonce fields or token parameters on state-changing actions such as saving settings, importing reviews, or deleting records
    Affected if No nonce token or anti-CSRF mechanism is found on sensitive forms

You are affected if the WP Google Review Slider plugin is installed with version 16.0 or lower and lacks anti-CSRF protections on its forms, allowing SQL injection via forged requests.

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

Update WP Google Review Slider to a version beyond 16.0. Implement anti-CSRF tokens on all state-changing actions and use prepared statements/parameterized queries to prevent SQL injection.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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