The AI Engine WordPress plugin before 3.7.2 does not confine a caller-supplied URL when mapping it to a local filesystem path before reading the file and forwarding its contents to an external service, allowing users with a subscriber-level account to read arbitrary files from the server and exfiltrate them off-host. Reaching the issue at subscriber level requires a non-default public API feature to be enabled; otherwise the same issue is reachable by an administrator, which on multisite allows a non-super subsite administrator to read the network-shared configuration and its secrets.
CVE-2026-75797
Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2026-08-26. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.7; sources differ by 0.0.
- 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(high)
- 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
- 31%
- KEV
- Not listed
Published
August 26, 2026
Last Modified
August 26, 2026
Advisory Details (1)
Auto-updated Aug 26, 2026AI Engine 3.3.3 – 3.7.1 – Subscriber+ Arbitrary File Read via 'url' Parameter | CVE 2026-75797 | Plugin Vulnerabilities
https://wpscan.com/vulnerability/1048b130-9263-4780-b886-656a891de85a/Vendor Advisories for CVE-2026-75797(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 18× in last 7d / 18× 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 02:03 UTCEG score recompute
- 2026-08-30 02:03 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 13:02 UTCGHSA enrichment
- 2026-08-28 23:59 UTCEG score recompute
- 2026-08-28 23:59 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 07:46 UTCGHSA enrichment
- 2026-08-27 18:42 UTCEG score recompute
- 2026-08-27 18:42 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 05:40 UTCEG score recompute
- 2026-08-27 05:40 UTCGHSA enrichment
- 2026-08-26 15:04 UTCEG score recompute▲ 7.70
- 2026-08-26 15:01 UTCMITRE cvelistV5CVSS v3 → 7.7 · severity → HIGH
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 06:10 UTCEG score recompute
- 2026-08-26 06:08 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-75797?
When was CVE-2026-75797 disclosed?
Is CVE-2026-75797 actively exploited?
What is the CVSS score of CVE-2026-75797?
How do I remediate CVE-2026-75797?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75797
Is Your Infrastructure Affected by CVE-2026-75797?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.