# CVE-2026-75797: AI Engine 3.3.3 - 3.7.1 - Subscriber+ Arbitrary File Read via 'url' Parameter

> Subscribers can read arbitrary server files and exfiltrate them if a specific public API feature is enabled, exposing sensitive configuration data.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-v7cm-6545-2w7m

## What is CVE-2026-75797?

CVE-2026-75797 is a high-severity path traversal vulnerability in Unknown AI Engine, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-75797?


## How do I fix CVE-2026-75797?

No fix has been published for CVE-2026-75797 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-75797 being exploited?

There is no known exploitation of CVE-2026-75797 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-75797 and fix it if it is affected.

What it is: CVE-2026-75797 is a high-severity path traversal vulnerability in Unknown AI Engine, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-75797 in the wild and no public exploit code.

Affected product: Unknown AI Engine. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-75797/ (Markdown: https://insights.sbomify.com/CVE-2026-75797/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-75797
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-75797
- OSV: https://osv.dev/vulnerability/CVE-2026-75797

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-75797/
Summaries are generated and may contain mistakes; the official description above is the record.