# CVE-2011-3744: HTML Purifier allows remote attackers to obtain sensitive information

> Remote attackers can obtain sensitive installation path information via direct requests to PHP files in HTML Purifier.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/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:** 23 Sep 2011
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-jw86-5cjf-mv79, UBUNTU-CVE-2011-3744

## What is CVE-2011-3744?

CVE-2011-3744 is a medium-severity vulnerability in n/a, published on 23 Sep 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HTML Purifier 4.2.0 allows remote attackers to obtain sensitive information via a direct request to a .php file, which reveals the installation path in an error message, as demonstrated by tests/PHPT/Reporter/SimpleTest.php and certain other files.

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

## Which versions are affected by CVE-2011-3744?

2 open source packages ship an affected version, including ezyang/htmlpurifier. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ezyang/htmlpurifier` | Packagist | All versions to 4.2.0 | None |
| `ezyang/htmlpurifier` | Packagist | All versions to 4.2.0 | None |

Products: Htmlpurifier Html Purifier.

## How do I fix CVE-2011-3744?

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

## Is CVE-2011-3744 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-3744 and fix it if it is affected.

What it is: CVE-2011-3744 is a medium-severity vulnerability in n/a, published on 23 Sep 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-3744 in the wild and no public exploit code.

Affected packages and fixed versions:
- ezyang/htmlpurifier (Packagist): affected all versions up to 4.2.0; no fix listed
- ezyang/htmlpurifier (Packagist): affected all versions up to 4.2.0; no fix listed

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-2011-3744/ (Markdown: https://insights.sbomify.com/CVE-2011-3744/index.md)
```

## Sources

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

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