CVE-2026-76203Network attack vector

Cross-user request forcing via CSS escape bypass

Published Aug 19, 2026 · Updated Aug 19, 2026

CSS sanitizer bypass in Maalfer Pentestify 1.2.0 through 2.3.2 allows remote authenticated users to force victim browsers to fetch attacker URLs. The sanitize_css_source() routine in backend/schemas.py applies a literal blocklist for url() before decoding CSS escapes, so sequences such as \75 rl( are reconstructed by the browser tokenizer after validation and survive into injected custom_css. Any authenticated account can store the theme through POST /api/themes or the global report_theme setting, causing every user who loads the application to disclose IP address and User-Agent to an attacker-controlled host without script execution.

CVSS severity5.1
Medium
EPSS probability0.29%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

CSS sanitizer bypass in Maalfer Pentestify 1.2.0 through 2.3.2 allows remote authenticated users to force victim browsers to fetch attacker URLs. The sanitize_css_source() routine in backend/schemas.py applies a literal blocklist for url() before decoding CSS escapes, so sequences such as \75 rl( are reconstructed by the browser tokenizer after validation and survive into injected custom_css. Any authenticated account can store the theme through POST /api/themes or the global report_theme setting, causing every user who loads the application to disclose IP address and User-Agent to an attacker-controlled host without script execution.

The record

CVE
CVE-2026-76203
Published
Aug 19, 2026
Updated
Aug 19, 2026
Vendor
Maalfer
Product
Pentestify
Classifications
CWE-180
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 19, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 19, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=1.2.0 <1ed1aad

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Maalfer · Pentestifyversion=1.2.0 <1ed1aad

Published CVSS scores

5.1Secur0CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-180Incorrect Behavior Order: Validate Before Canonicalize

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo