# CVE-2026-15021: wpForo Forum <= 3.1.1 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'location' Profile Field

> Authenticated attackers can inject arbitrary scripts via the location profile field, leading to code execution when other users view the profile.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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:** 16 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** GHSA-76cp-m73j-f6wq

## What is CVE-2026-15021?

CVE-2026-15021 is a medium-severity cross-site scripting vulnerability in tomdever wpForo Forum, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The wpForo Forum plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'location' Profile Field in all versions up to, and including, 3.1.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The sanitize_text_field() function applied at input does not encode double quotes, allowing attribute breakout via a payload that escapes the href attribute context and injects event handler attributes.

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

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


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

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

## Is CVE-2026-15021 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15021 is a medium-severity cross-site scripting vulnerability in tomdever wpForo Forum, published on 16 Jul 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-15021 in the wild and no public exploit code.

Affected product: tomdever wpForo Forum. 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-15021/ (Markdown: https://insights.sbomify.com/CVE-2026-15021/index.md)
```

## Sources

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

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