# CVE-2026-111979: GiveWP < 4.19.0.1 - Give Worker+ Stored XSS via Form Template Primary Color


- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-xm8r-m35h-qq8p

## What is CVE-2026-111979?

CVE-2026-111979 is a medium-severity vulnerability in Unknown GiveWP, published on 25 Oct 2026. 

### Official description

The GiveWP  WordPress plugin before 4.19.0.1 does not properly sanitise and escape one of its donation form template settings before outputting it inside an HTML attribute, allowing users with a custom form-editing GiveWP  WordPress plugin before 4.19.0.1 role to inject arbitrary web scripts that execute in the browser of any visitor or administrator who opens the affected donation form.

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

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


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

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

## Is CVE-2026-111979 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111979 is a medium-severity vulnerability in Unknown GiveWP, published on 25 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-111979 in the wild and no public exploit code.

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

## Sources

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

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