dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-6189

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-10
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 Duplicate Page and Post plugin for WordPress is vulnerable to time-based SQL Injection via the ‘meta_key’ parameter in all versions up to, and including, 2.9.5 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 Duplicate Page and Post WordPress plugin fails to properly escape the user-supplied 'meta_key' parameter and lacks prepared statements in its SQL queries. This allows authenticated attackers with Contributor-level or higher access to inject arbitrary SQL statements, enabling time-based blind SQL injection to extract sensitive data from the database.

MitigationUpdate the plugin to version 2.9.6 or later which contains the patch. Until then, limit user permissions to roles below Contributor and monitor for suspicious database query patterns.

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. Identify if the Duplicate Page and Post plugin is installed
    Navigate to Plugins > Installed Plugins in WordPress admin and search for 'Duplicate Page and Post', or check the /wp-content/plugins/ directory for the plugin folder
    Affected if The plugin is present in the WordPress installation
  2. Check the installed plugin version
    In the WordPress admin_plugins list, find the version number listed for the Duplicate Page and Post plugin, or inspect the plugin's main PHP file for the Version header comment
    Affected if The installed version is lower than 2.9.6 (e.g., 2.9.5, 2.9.4, earlier versions)
  3. Verify the plugin is active
    Check the WordPress plugins page to confirm the Duplicate Page and Post plugin has the 'Active' status
    Affected if The plugin is currently activated and accessible to authenticated users
  4. Confirm Contributor-level or higher user accounts exist
    Navigate to Users > All Users in WordPress admin and review the role column, or query the wp_usermeta table for users with roles of Contributor, Author, Editor, or Administrator
    Affected if At least one user account has Contributor-level access or higher, enabling them to trigger the vulnerable parameter
  5. Inspect for the vulnerable meta_key parameter in requests
    Review web server access logs or WordPress debug logs for requests to /wp-admin/admin-ajax.php or similar endpoints containing the 'meta_key' parameter, or use a proxy to capture plugin-related AJAX calls
    Affected if Requests containing the meta_key parameter are being processed by the plugin without proper preparation

The environment is affected if the Duplicate Page and Post plugin is installed, active, running version below 2.9.6, and any Contributor-level or higher user account exists who could inject SQL via the meta_key parameter.

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 2.9.6 or later which contains the patch. Until then, limit user permissions to roles below Contributor and monitor for suspicious database query patterns.

Recommended fix High confidence

Version 2.9.6 or later of the Duplicate Page and Post WordPress plugin

  1. Backup your WordPress site database and files before making any changes
  2. Update the Duplicate Page and Post plugin to version 2.9.6 or later via WordPress admin dashboard (Plugins > Updates), or upload the latest version from wordpress.org
  3. After updating, verify the plugin is active and functioning correctly
  4. Confirm the vulnerability is patched by ensuring the meta_key parameter is now properly escaped in plugin queries
Caveat Minimal risk - this is a security patch update; test duplicate post functionality after upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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