# CVE-2018-25329: WordPress Plugin WP with Spritz 1.0 Remote File Inclusion

> Unauthenticated attackers can read arbitrary files via path traversal in the WP with Spritz plugin, exposing sensitive system data.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 May 2026
- **Updated:** 18 May 2026
- **Also known as:** GHSA-538v-9qx2-525c

## What is CVE-2018-25329?

CVE-2018-25329 is a high-severity path traversal vulnerability in wp-with-spritz WP with Spritz, published on 17 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WordPress Plugin WP with Spritz 1.0 contains a remote file inclusion vulnerability that allows unauthenticated attackers to read arbitrary files by injecting file paths into the url parameter. Attackers can send GET requests to wp.spritz.content.filter.php with malicious url values to access sensitive files like system configuration and credentials.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

## Which versions are affected by CVE-2018-25329?


## How do I fix CVE-2018-25329?

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

## Is CVE-2018-25329 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25329 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25329 and fix it if it is affected.

What it is: CVE-2018-25329 is a high-severity path traversal vulnerability in wp-with-spritz WP with Spritz, published on 17 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25329 exists.

Affected product: wp-with-spritz WP with Spritz. 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-2018-25329/ (Markdown: https://insights.sbomify.com/CVE-2018-25329/index.md)
```

## Sources

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

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