# CVE-2026-76203: CSS sanitizer bypass in Pentestify report themes allows forced outbound requests

> Authenticated users can bypass CSS sanitization to force outbound requests, disclosing victim IP addresses and User-Agent strings.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-6xgw-5q2h-p29f

## What is CVE-2026-76203?

CVE-2026-76203 is a medium-severity server-side request forgery vulnerability in maalfer Pentestify, published on 19 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Incorrect Behavior Order: Validate Before Canonicalize in the report theme CSS sanitizer
in maalfer Pentestify 1.2.0 through 2.3.2 allows an authenticated user to force outbound
HTTP requests from other users' browsers, disclosing their IP address and User-Agent, via
CSS hex escapes that reconstruct the url() function and evade the sanitizer blocklist

Weakness: CWE-180 (Incorrect Behavior Order: Validate Before Canonicalize)

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


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

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

## Is CVE-2026-76203 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76203 is a medium-severity server-side request forgery vulnerability in maalfer Pentestify, published on 19 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-76203 in the wild and no public exploit code.

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

## Sources

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

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