dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-5563

MEDIUM · 6.5 CVSS v3.1 Published 2025-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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-Addpub plugin for WordPress is vulnerable to SQL Injection via the 'wp-addpub' shortcode in all versions up to, and including, 1.2.8 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 WP-Addpub WordPress plugin suffers from a SQL Injection vulnerability in its 'wp-addpub' shortcode (versions up to 1.2.8). The vulnerability stems from two combined issues: insufficient escaping of user-supplied parameters and lack of prepared statements in the SQL query. An attacker with Contributor-level access or higher can inject malicious SQL queries to extract sensitive database information.

MitigationUpdate the WP-Addpub plugin to the latest version immediately. If no patched version is available, disable and remove the plugin until a fix is released. Alternatively, remove the shortcode functionality from the codebase as a temporary workaround.

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 WP-Addpub plugin is installed
    Access WordPress admin > Plugins and look for WP-Addpub in the list of installed plugins, or use WP-CLI: wp plugin list --search='*addpub*'
    Affected if WP-Addpub appears in the installed plugins list
  2. Determine installed plugin version
    View the plugin details page in WordPress admin (click on the plugin name) to see the version number, or inspect the main plugin file header in wp-content/plugins/wp-addpub/ for the 'Version' comment
    Affected if Version displayed is 1.2.8 or lower (any version up to and including 1.2.8)
  3. Identify if the vulnerable shortcode is in use
    Search your WordPress database or content for the shortcode [wp-addpub] appearing in posts, pages, or widgets. In WP-CLI: wp post list --s='[wp-addpub]' --format=ids
    Affected if The shortcode [wp-addpub] is present in any published content
  4. Assess user access levels
    Review user accounts with Contributor, Author, Editor, or Administrator roles in WordPress admin > Users. These roles can execute the shortcode.
    Affected if Any user account with Contributor-level access or higher exists on the site

Your environment is affected if WP-Addpub plugin is installed with version 1.2.8 or lower AND the wp-addpub shortcode is present in any content AND at least one user with Contributor-level access or higher exists.

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 WP-Addpub plugin to the latest version immediately. If no patched version is available, disable and remove the plugin until a fix is released. Alternatively, remove the shortcode functionality from the codebase as a temporary workaround.

Recommended fix Moderate confidence

Version 1.2.9 or later (check WordPress Plugin Repository for latest stable release)

  1. Check the current version of the WP-Addpub plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate WP-Addpub and note the current version number
  4. Visit the WordPress Plugin Repository at https://wordpress.org/plugins/wp-addpub/ to verify if a version newer than 1.2.8 is available
  5. If version 1.2.9 or higher is available, update the plugin via Plugins > Add New > Upload or directly from the Plugins page
  6. After updating, verify the fix was applied by confirming the plugin version has changed
Caveat Review plugin settings after upgrade as minor configuration changes may occur with security updates

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,010
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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