# CVE-2016-15039: mhuertos phpLDAPadmin ajax_functions.js makeHttpRequest request smuggling

> Remote attackers can exploit HTTP request smuggling in phpLDAPadmin's AJAX functions, potentially leading to cache poisoning or session hijacking.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Jul 2024
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-15039, GHSA-h87m-6ppf-r3wm, UBUNTU-CVE-2016-15039

## What is CVE-2016-15039?

CVE-2016-15039 is a medium-severity vulnerability in mhuertos phpLDAPadmin, published on 11 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability classified as critical was found in mhuertos phpLDAPadmin up to 665dbc2690ebeb5392d38f1fece0a654225a0b38. Affected by this vulnerability is the function makeHttpRequest of the file htdocs/js/ajax_functions.js. The manipulation leads to http request smuggling. The attack can be launched remotely. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The patch is named dd6e9583a2eb2ca085583765e8a63df5904cb036. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-270523.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

## Which versions are affected by CVE-2016-15039?


## How do I fix CVE-2016-15039?

Apply the vendor's patch.

## Is CVE-2016-15039 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-15039 and fix it if it is affected.

What it is: CVE-2016-15039 is a medium-severity vulnerability in mhuertos phpLDAPadmin, published on 11 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-15039 in the wild and no public exploit code.

Affected product: mhuertos phpLDAPadmin. 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-2016-15039/ (Markdown: https://insights.sbomify.com/CVE-2016-15039/index.md)
```

## Sources

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

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