# CVE-2025-15675: Charitable < 1.8.5.3 - Admin+ Stored XSS via Photo Field ALT Text

> High-privilege users can inject malicious scripts via campaign image alt text, leading to stored XSS on front-end pages.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-pwhm-f4mm-grcw

## What is CVE-2025-15675?

CVE-2025-15675 is a medium-severity cross-site scripting vulnerability in Unknown Charitable, published on 2 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The Charitable  WordPress plugin before 1.8.5.3 does not sanitise and escape one of its campaign image text fields before outputting it in an HTML attribute, allowing users with a high-privilege campaign-management role to perform Stored Cross-Site Scripting attacks that execute on the front-end campaign page.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-15675?


## How do I fix CVE-2025-15675?

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

## Is CVE-2025-15675 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15675 and fix it if it is affected.

What it is: CVE-2025-15675 is a medium-severity cross-site scripting vulnerability in Unknown Charitable, published on 2 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15675 exists.

Affected product: Unknown Charitable. 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-2025-15675/ (Markdown: https://insights.sbomify.com/CVE-2025-15675/index.md)
```

## Sources

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

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