The SmartAIPress WordPress plugin through 1.2.0 does not perform a capability check on one of its AJAX actions and does not validate a user-supplied URL before fetching it server-side, allowing users with subscriber-level access and above to make the site retrieve arbitrary internal or external URLs and read the response, resulting in a full-read Server-Side Request Forgery.
CVE-2026-16600
This high-severity CVE scores 7.7 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.7
- EG Score
- 7.7(medium)
- EG Risk
- 35(Track)EG Risk 35/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity77% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
August 29, 2026
Last Modified
August 30, 2026
Advisory Details (1)
Auto-updated Aug 30, 2026SmartAIPress <= 1.2.0 – Subscriber+ Server-Side Request Forgery via smartaipress_openai_upload_and_set_featured_image | CVE 2026-16600 | Plugin Vulnerabilities
https://wpscan.com/vulnerability/66d2dc2d-fe77-4d34-bfca-d47b086a9c96/Vendor Advisories for CVE-2026-16600(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:30 UTCEG score recompute
- 2026-08-30 01:30 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-30 01:09 UTCEG score recompute▲ 7.70
- 2026-08-30 01:09 UTCGHSA enrichment
- 2026-08-30 01:08 UTCMITRE cvelistV5CVSS v3 → 7.7 · severity → HIGH
- 2026-08-29 06:21 UTCNVD update
- 2026-08-29 06:14 UTCEG score recompute
- 2026-08-29 06:12 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p91CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(5)
What is CVE-2026-16600?
When was CVE-2026-16600 disclosed?
Is CVE-2026-16600 actively exploited?
What is the CVSS score of CVE-2026-16600?
How do I remediate CVE-2026-16600?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16600
Is Your Infrastructure Affected by CVE-2026-16600?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.