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

CVE-2025-53317

HIGH · 7.1 CVSS v3.1 Published 2025-06-27
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 AcmeeDesign WPShapere - WordPress admin theme wpshapere-lite allows Stored XSS.This issue affects WPShapere - WordPress admin theme: from n/a through <= 1.4.1.

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

CSRF vulnerability in WPShapere admin theme enables attackers to trick authenticated administrators into submitting malicious requests that inject stored XSS payloads. Since XSS is stored, the malicious script executes for all users viewing affected admin pages.

MitigationImplement anti-CSRF tokens on all state-changing admin actions and apply proper input sanitization/output encoding to prevent XSS. Update to patched version when available from vendor.

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. Identify if WPShapere is installed
    Check the WordPress plugins or themes directory for the WPShapere admin theme. In WordPress admin, go to Appearance > Themes to see if WPShapere is an active or installed theme. Alternatively, check the /wp-content/themes/ directory for a folder named 'wpshapere' or similar.
    Affected if WPShapere admin theme is installed as an active or available theme in the WordPress installation
  2. Determine the WPShapere version
    If WPShapere is found, check its style.css or main PHP file for the version comment header (e.g., 'Version: x.x.x'). In WordPress admin, go to Themes > WPShapere theme details if available. Check the theme files directly via file system access.
    Affected if The installed version matches or falls within the vulnerable version range (contact vendor for specific affected versions)
  3. Verify admin access to WPShapere settings
    Log in to WordPress admin panel and navigate to the WPShapere theme settings panel (usually under Appearance > WPShapere or a dedicated admin menu item). Attempt to access any configuration pages where admin settings can be modified.
    Affected if Admin can access WPShapere configuration pages, indicating the vulnerable functionality is present
  4. Inspect admin pages for stored XSS indicators
    View the source HTML of WPShapere admin pages in a browser. Look for unescaped user-controlled parameters in forms or settings pages. Check if input fields reflect values without proper encoding.
    Affected if Admin pages contain reflected or stored content without proper output encoding, suggesting the XSS injection point exists
  5. Check for anti-CSRF protection on admin actions
    Examine the WPShapere admin PHP files for presence of nonce verification or CSRF tokens. Search for 'wp_nonce_field', 'check_admin_referer', or similar WordPress security functions in the theme's admin submission handlers.
    Affected if Admin action handlers lack nonce verification or CSRF token checks, confirming the vulnerability is exploitable

A user is affected if WPShapere admin theme is installed, the version is unpatched, and the admin panel with its settings functionality is accessible without proper CSRF and XSS protections in place.

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 on all state-changing admin actions and apply proper input sanitization/output encoding to prevent XSS. Update to patched version when available from vendor.

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-53317 — 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-53317 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