dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-57643

HIGH · 8.5 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable Zero-click 8 weeks old

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
Contributor SQL Injection in WP Post Author <= 3.9.1 versions.

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

SQL injection vulnerability in the WP Post Author WordPress plugin allows authenticated users with Contributor role to inject malicious SQL queries via unsanitized input. The vulnerability exists in versions 3.9.1 and below, potentially allowing attackers to access, modify, or delete database content.

MitigationUpdate WP Post Author plugin to a version beyond 3.9.1. If no patched version is available, remove the plugin or implement Web Application Firewall rules to block SQL injection attempts.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 WP Post Author plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'WP Post Author' in the list, or inspect the /wp-content/plugins/ directory for the wp-post-author folder.
    Affected if The plugin appears in the installed plugins list.
  2. Determine installed plugin version
    In the Plugins list, click on the plugin name to view details, or inspect the main plugin file (e.g., wp-post-author.php) and look for the 'Version:' header in the plugin comments.
    Affected if The reported version is 3.9.1 or any version below it.
  3. Confirm Contributor role users exist
    In WordPress admin, go to Users > All Users and check if any users have the 'Contributor' role assigned.
    Affected if At least one user account with Contributor role exists on the site.
  4. Verify plugin is active
    In the Plugins list, check if WP Post Author shows as 'Active' under the plugin status column.
    Affected if The plugin is currently activated.

A user is affected if the WP Post Author plugin is installed with version 3.9.1 or below AND the plugin is active AND there is at least one Contributor-level user account on the site.

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 WP Post Author plugin to a version beyond 3.9.1. If no patched version is available, remove the plugin or implement Web Application Firewall rules to block SQL injection attempts.

Recommended fix Moderate confidence

WP Post Author 3.9.2 or latest available version

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'WP Post Author' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, download the latest version from the WordPress Plugin Repository and upload it manually
  6. 6. After updating, verify the plugin is running version 3.9.2 or higher

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
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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