PublishPress Authors blind SQL injection in author plugin
- Exploited
- No known exploitation
- Fix
- Fixed in 4.20.0
- Who is exposed
- Specific setups only
Summary
The PublishPress Authors plugin for WordPress, from PublishPress, has a blind SQL injection flaw. An attacker with low-privilege login can exploit it remotely over the network, without any action from a user, to inject database commands.
Written by a model
Original description
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in PublishPress PublishPress Authors publishpress-authors allows Blind SQL Injection.This issue affects PublishPress Authors: from n/a through 4.18.0.
What to do
Upgrade to a fixed version: 4.20.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-122676 (WordPress PublishPress Authors plugin <= 4.18.0 - SQL Injection vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-122676 (entry last updated 2026-11-19):
Affected:
- PublishPress PublishPress Authors: fixed in 4.20.0
Fixed versions: 4.20.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-122676 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-122676 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/publishpress-authors/vulnerability/wordpress-publishpress-authors-plugin-4-18-0-sql-injection-vulnerability?_s_id=cve
- https://www.cve.org/CVERecord?id=CVE-2026-122676
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-122676
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-122676"}.Affected versions
- publishpress-authorsfixed in 4.20.0 · through 4.18.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.5/10CVSS 8.5
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-122676 |
| Record | NVD · CVE-2026-122676 |
| Other links 1 | |
| Link | patchstack.com · database/wordpress/plugin/publishpress-authors/vulnerability/wordpress-publishpress-authors-plugin-4-18-0-sql-injection-vulnerability?_s_id=cve |
Questions about CVE-2026-122676
Is CVE-2026-122676 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The plugin has an SQL injection flaw, which lets an attacker run database queries through input the plugin does not properly handle. The advisory says an attacker could read, modify, or delete the entire database, including user accounts and private data.
Source: patchstack.com, cve.org
Which versions are affected by CVE-2026-122676?
publishpress-authors: through 4.18.0 (fixed in 4.20.0).
Source: cve.now feed data
Am I affected, and how do I check?
Versions of the PublishPress Authors WordPress plugin up to and including 4.18.0 are affected. To check a site, look at the plugin version shown on the WordPress Plugins page or in the plugin's header.
Source: patchstack.com, cve.org
How do I fix CVE-2026-122676?
Update the PublishPress Authors plugin to version 4.20.0 or later, the first fixed release.
Source: patchstack.com, cve.org
Related
- CVE-2024-9215Co-Authors, Multiple Authors and Guest Authors in an Author Box with PublishPress Authors <= 4.7.1 - Insecure Direct Object Reference to Authenticated (Author+) Arbitrary User Email Update and Account Takeover
- CVE-2025-26886WordPress PublishPress Authors plugin <= 4.7.3 - SQL Injection vulnerability
- CVE-2026-25309WordPress PublishPress Authors plugin <= 4.10.1 - Broken Access Control vulnerability
- CVE-2025-47496WordPress PublishPress Authors plugin <= 4.7.5 - Local File Inclusion Vulnerability
- CVE-2026-115610WordPress PublishPress Authors plugin <= 4.17.0 - Cross Site Scripting (XSS) vulnerability
- CVE-2026-111592Co-Authors, Multiple Authors and Guest Authors in an Author Box with PublishPress Authors <= 4.17.0 - Authenticated (Subscriber+) Stored…
No corrections so far. Something wrong on this page? Report an error.