dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-12800

MEDIUM · 6.4 CVSS v3.1 Published 2025-11-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 Server-Side Request Forgery in all versions up to, and including, 7.4.5 via the su_shortcode_csv_table function. This makes it possible for authenticated attackers, with Administrator-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. If the 'Unsafe features' option is explicitly enabled by an administrator, this issue becomes exploitable by Contributor+ attackers

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

The Shortcodes Ultimate WordPress plugin contains an SSRF vulnerability in the su_shortcode_csv_table function. Authenticated attackers with Administrator-level access (or Contributor+ if 'Unsafe features' is enabled) can make arbitrary web requests from the server, potentially accessing internal services and exfiltrating data.

MitigationUpdate the plugin to version 7.4.6 or later, which should contain proper URL validation in the su_shortcode_csv_table function to prevent SSRF attacks. Until then, ensure the 'Unsafe features' option remains disabled and restrict Administrator-level access.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Check the installed plugin version
    In WordPress admin, go to Plugins > Shortcodes Ultimate and note the version number, or check the plugin header in /wp-content/plugins/shortcodes-ultimate/includes/functions.php for the 'Version' constant
    Affected if The installed version is lower than 7.4.6
  2. Verify the Unsafe features setting
    In WordPress admin, go to Shortcodes Ultimate > Settings > Advanced (or General tab) and look for the 'Unsafe features' checkbox
    Affected if The 'Unsafe features' option is enabled (checked)
  3. Confirm Administrator role presence
    In WordPress admin, go to Users and review which accounts have the Administrator role, or query wp_usermeta for users with wp_capabilities containing 'administrator'
    Affected if There are any Administrator-level accounts (these users can trigger the vulnerability regardless of other settings)
  4. Check for Contributor+ role access if Unsafe features is off
    If Unsafe features is disabled, verify if any users have Contributor or Author roles who could potentially elevate or if the site allows contributor+ user registration
    Affected if Contributor or higher role users exist AND Unsafe features is enabled, lowering the exploitation threshold
  5. Inspect for csv_table shortcode usage
    Search post content in wp_posts or use WordPress search to find instances of [csv_table] shortcode being used in pages or posts
    Affected if The csv_table shortcode is actively in use, making the attack surface visible

A user is affected if their installed version is below 7.4.6 AND they have Administrator users (or Contributor+ users with Unsafe features enabled) who can access the csv_table shortcode functionality.

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 the plugin to version 7.4.6 or later, which should contain proper URL validation in the su_shortcode_csv_table function to prevent SSRF attacks. Until then, ensure the 'Unsafe features' option remains disabled and restrict Administrator-level access.

Recommended fix High confidence

7.4.6 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Shortcodes Ultimate' plugin
  4. Check the current version is 7.4.5 or below
  5. Click 'Update now' if an update is available, or manually download version 7.4.6 or later from the WordPress plugin repository
  6. Verify the update was successfully applied

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