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

CVE-2025-30572

HIGH · 7.1 CVSS v3.1 Published 2025-03-24
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
Cross-Site Request Forgery (CSRF) vulnerability in Igor Yavych Simple Rating simple-rating allows Stored XSS.This issue affects Simple Rating: from n/a through <= 1.4.

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 Simple Rating plugin allows attackers to inject malicious JavaScript code through form submissions. When an authenticated administrator or user clicks a crafted link, the attacker's request is executed without proper token validation, and the malicious payload is stored (Stored XSS), executing whenever other users view the rating content.

MitigationImplement anti-CSRF tokens (nonces) on all form submissions in the plugin and add proper input sanitization/output encoding to prevent stored XSS. Additionally, set SameSite attributes on session cookies.

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. Locate Simple Rating plugin installation
    Search for plugin files named 'simple-rating', 'simple-rating-plugin', or similar in common plugin directories (wp-content/plugins/ for WordPress, or application's plugin folder). Identify the exact plugin folder name and version file.
    Affected if The Simple Rating plugin is found installed in the environment.
  2. Inspect form submission handlers for nonce validation
    Open PHP files handling form submissions (typically in main plugin file or handlers directory). Search for 'wp_nonce_field', 'wp_verify_nonce', 'nonce', 'csrf_token', or 'token' validation calls within form processing logic.
    Affected if Form handlers do not contain nonce/token validation calls - the vulnerability exists if forms submit without verifying a CSRF token.
  3. Check input sanitization on form data
    Examine code that processes submitted form values (rating values, comment fields, user inputs). Look for sanitization functions like 'sanitize_text_field', 'esc_html', 'esc_attr', or similar escaping functions applied to user input before storage.
    Affected if User-submitted data is stored without sanitization functions or output encoding is missing.
  4. Verify stored data output encoding
    Locate code that retrieves and displays rating data (when users view ratings). Check if output functions include encoding (esc_html, esc_attr, or similar) when rendering stored values to the page.
    Affected if Stored rating data is rendered to HTML without proper output encoding, enabling stored XSS.
  5. Review cookie configuration for SameSite attribute
    Check plugin initialization code and session configuration for Set-Cookie headers or session cookie definitions. Look for 'SameSite' attribute being set to 'Strict' or 'Lax'.
    Affected if Session cookies lack SameSite attribute configuration.

The environment is affected if the Simple Rating plugin is installed AND form submissions lack CSRF token validation AND user input is stored without sanitization, allowing stored XSS execution.

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

Implement anti-CSRF tokens (nonces) on all form submissions in the plugin and add proper input sanitization/output encoding to prevent stored XSS. Additionally, set SameSite attributes on session cookies.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-30572 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