CSS sanitizer bypass in Pentestify report themes allows forced outbound requests
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| maalfer | Pentestify | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Maalfer | Pentestify |
|
Vendor Solution
Tagged releases v2.0.0, v2.2.0, v2.3.0 and v2.3.2 shipped vulnerable. v1.1.1 is not affected (no custom_css field). The fix is not tagged and does not bump the version constant, so the upper bound cannot be stated as a version until a release is cut. It´s recommended to install from the repository.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.397% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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 | |
| Title | CSS sanitizer bypass in Pentestify report themes allows forced outbound requests | |
| First Time appeared |
Maalfer
Maalfer pentestify |
|
| Weaknesses | CWE-180 | |
| CPEs | cpe:2.3:a:maalfer:pentestify:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Maalfer
Maalfer pentestify |
|
| References |
| |
| Metrics |
cvssV4_0
|