CVE-2025-26886
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in PublishPress PublishPress Authors publishpress-authors allows SQL Injection.This issue affects PublishPress Authors: from n/a through <= 4.7.3.
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 confidenceSQL injection vulnerability in PublishPress Authors WordPress plugin allows attackers to inject malicious SQL commands through unsanitized input that gets incorporated into database queries. The flaw exists in versions through 4.7.3 and could allow unauthorized data extraction or modification.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify PublishPress Authors plugin is installedLog into WordPress admin and navigate to Plugins > Installed Plugins, or use command: wp plugin list --name=publishpress-authorsAffected if Plugin is not installed or not present in the WordPress installation
-
Check installed plugin versionIn WordPress admin, click on the plugin to view details and note the version number; alternatively, check the plugin main file header: wp plugin path/wp-authors/plugin.php and look for 'Version:' tagAffected if Installed version is 4.7.3 or any earlier version through the 4.x line
-
Confirm plugin is activeIn WordPress admin > Plugins, verify the PublishPress Authors plugin shows as 'Active', or run: wp plugin status publishpress-authorsAffected if Plugin is active - only active plugins can execute their code and be exploited
-
Identify if plugin handles user inputReview any publicly accessible forms, shortcodes, or API endpoints created by PublishPress Authors that accept user input (author submissions, search, filter parameters)Affected if User-facing input fields exist and are processed by the plugin without sanitization
User is affected if PublishPress Authors plugin version 4.7.3 or earlier is installed and active, and the plugin processes user-supplied input that reaches database queries without prepared statements.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate PublishPress Authors to the latest version after patches are released, or apply parameterized queries/prepared statements to any user input used in SQL queries within the plugin code.
PublishPress Authors 4.7.4 or latest available version
- Check your current PublishPress Authors plugin version in WordPress admin under Plugins
- Navigate to Plugins > Add New > Upload or update directly from Plugins page
- Ensure you have a full backup of your WordPress site before updating
- Update PublishPress Authors to the latest version available in the WordPress plugin repository
- Verify the update completed successfully and test that the plugin functions normally
- Check that the new version is 4.7.4 or higher which should contain the fix for this SQL injection vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26886 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-26886 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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