# CVE-2024-32825: WordPress Simply Static plugin <= 3.1.3 - Sensitive Data Exposure via Log File vulnerability

> Attackers can access sensitive data exposed in log files generated by the Simply Static WordPress plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-26f4-xfjh-462v

## What is CVE-2024-32825?

CVE-2024-32825 is a high-severity vulnerability in Simply Static, published on 24 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insertion of Sensitive Information Into Sent Data vulnerability in Simply Static Simply Static simply-static.This issue affects Simply Static: from n/a through <= 3.1.3.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

## Which versions are affected by CVE-2024-32825?


## How do I fix CVE-2024-32825?

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

## Is CVE-2024-32825 being exploited?

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

Public exploit code:

- Simply Static - Information Disclosure (nuclei): http/cves/2024/CVE-2024-32825.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-32825 and fix it if it is affected.

What it is: CVE-2024-32825 is a high-severity vulnerability in Simply Static, published on 24 Apr 2024. 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-2024-32825 exists.

Affected product: Simply Static. 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-2024-32825/ (Markdown: https://insights.sbomify.com/CVE-2024-32825/index.md)
```

## Sources

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

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