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

CVE-2025-52797

HIGH · 8.2 CVSS v3.1 Published 2025-08-14
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 josepsitjar StoryMap wp-storymap allows SQL Injection.This issue affects StoryMap: from n/a through <= 2.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

Cross-Site Request Forgery (CSRF) vulnerability in the WordPress StoryMap plugin (wp-storymap) enables attackers to craft malicious requests that trigger SQL injection attacks. The lack of proper anti-CSRF token validation on sensitive plugin functions allows authenticated attackers to inject arbitrary SQL commands via forged requests.

MitigationUpdate to a patched version of the StoryMap plugin when available; implement anti-CSRF tokens (nonces) on all state-changing operations and use prepared statements for database queries.

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. Verify StoryMap plugin is installed and active
    Log in to WordPress admin panel and navigate to Plugins > Installed Plugins. Locate 'StoryMap' or 'wp-storymap' in the list and confirm it shows as 'Active'. Alternatively, check the /wp-content/plugins/ directory for the wp-storymap folder and inspect the main plugin file for version information.
    Affected if The plugin is installed and active, making the CSRF-to-SQLi vulnerability potentially exploitable.
  2. Identify installed StoryMap plugin version
    In WordPress admin, click on the StoryMap plugin to view details and note the version number. Alternatively, open the main plugin PHP file (usually wp-storymap.php or similar) in /wp-content/plugins/ and look for the 'Version' header in the plugin comment block.
    Affected if The installed version is unknown or falls within an unpatched version range (compare your version to any official security advisory).
  3. Check for state-changing plugin functions without nonce validation
    Review the plugin source code in /wp-content/plugins/wp-storymap/ for PHP functions that modify data (add, edit, delete, update operations). Search for absence of 'wp_verify_nonce', 'check_admin_referer', or nonce field generation in form handling and AJAX endpoints. Use grep or a code editor to search for vulnerable function patterns.
    Affected if Functions that perform database operations lack anti-CSRF token (nonce) validation, allowing forged requests to trigger SQL injection.
  4. Inspect database query handling for prepared statements
    Examine plugin PHP files for direct SQL query construction using $wpdb->query, $wpdb->prepare, or similar. Check if queries use parameterized/prepared statements with placeholders (%s, %d) or if user input is concatenated directly into SQL strings without sanitization.
    Affected if Database queries concatenate user-supplied input without prepared statements, enabling SQL injection when combined with the CSRF flaw.

Your environment is affected if the StoryMap plugin is active, lacks anti-CSRF nonce protection on sensitive functions, and uses unsanitized database queries that could be triggered via forged requests from an authenticated user.

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 to a patched version of the StoryMap plugin when available; implement anti-CSRF tokens (nonces) on all state-changing operations and use prepared statements for database queries.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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