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

CVE-2025-7369

MEDIUM · 6.1 CVSS v3.1 Published 2025-07-21
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

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 Shortcodes Plugin — Shortcodes Ultimate plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 7.4.2. This is due to missing or incorrect nonce validation on the preview function. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes via a forged request, granted they can trick a site administrator into performing an action such as clicking on a link. In combination with CVE-2025-7354, it leads to Reflected Cross-Site Scripting.

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

CSRF vulnerability in Shortcodes Ultimate WordPress plugin's preview function due to missing/nonce validation. Allows unauthenticated attackers to trick administrators into executing arbitrary shortcodes via forged requests. When combined with CVE-2025-7354, enables reflected XSS attacks.

MitigationUpdate Shortcodes Ultimate plugin to version 7.4.3 or later which includes proper nonce validation on the preview function, or implement CSRF token verification on the affected endpoint.

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 Shortcodes Ultimate plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Shortcodes Ultimate' in the list. Alternatively, check the /wp-content/plugins/shortcodes-ultimate/ directory exists on the server.
    Affected if The plugin is installed and active in WordPress
  2. Check installed plugin version
    In WordPress admin, find Shortcodes Ultimate in the Plugins list and note the version number displayed under the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/shortcodes-ultimate/shortcodes-ultimate.php for the 'Version' tag.
    Affected if Version is lower than 7.4.3 (the vulnerable version range)
  3. Confirm preview functionality is accessible
    Check if the WordPress site has the shortcodes preview endpoint exposed. This typically involves /wp-admin/admin-ajax.php calls with action 'su_preview_shortcode' or similar preview-related AJAX actions. Check if these endpoints respond without requiring authentication.
    Affected if The preview AJAX endpoint is accessible and responds to requests
  4. Verify absence of nonce validation on preview endpoint
    Examine the plugin source code in /wp-content/plugins/shortcodes-ultimate/includes/ajax/preview.php or similar preview handler files. Look for wp_verify_nonce or check_admin_referer calls at the beginning of the preview function. If no nonce check exists before processing shortcode output, the vulnerability is present.
    Affected if The preview handler lacks nonce verification (no wp_verify_nonce or check_admin_referer call found)

User is affected if Shortcodes Ultimate plugin version is below 7.4.3 and the preview function endpoint is accessible without nonce validation.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Shortcodes Ultimate plugin to version 7.4.3 or later which includes proper nonce validation on the preview function, or implement CSRF token verification on the affected endpoint.

Recommended fix High confidence

Version 7.4.3 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Shortcodes Ultimate plugin
  4. If an update is available, click 'Update Now' to update to the latest version
  5. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload the latest version from wordpress.org/plugins/shortcodes-ultimate/
  6. After updating, verify the version number reflects the latest release (7.4.3 or later)

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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