# CVE-2024-33437: Information disclosure in n/a

> A remote attacker can obtain sensitive information due to missing support for CSS Style Rules in the CSS Exfil Protection extension.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Apr 2024
- **Updated:** 28 Mar 2025
- **Also known as:** GHSA-q3p5-hqpp-3phh

## What is CVE-2024-33437?

CVE-2024-33437 is a high-severity vulnerability in n/a, published on 30 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in CSS Exfil Protection v.1.1.0 allows a remote attacker to obtain sensitive information due to missing support for CSS Style Rules.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-33437?

It affects 1 product.


Products: Mikegualtieri Css Exfil Protection.

## How do I fix CVE-2024-33437?

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

## Is CVE-2024-33437 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-33437 exists.

## Other vulnerabilities in n/a

- [CVE-2024-29384](https://insights.sbomify.com/CVE-2024-29384/): Information disclosure in n/a (high 7.5)
- [CVE-2024-33436](https://insights.sbomify.com/CVE-2024-33436/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-33437 and fix it if it is affected.

What it is: CVE-2024-33437 is a high-severity vulnerability in n/a, published on 30 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-33437 exists.

Affected product: n/a. 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-2024-33437/ (Markdown: https://insights.sbomify.com/CVE-2024-33437/index.md)
```

## Sources

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

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