# CVE-2016-0957: Security feature bypass in n/a

> Remote attackers can bypass dispatcher rules in Adobe Experience Manager due to improper URL filter implementation, potentially exposing protected resources.

- **Severity:** High 7.5 (`CVSS:3.0/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:** 10 Feb 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pw75-rg34-vpr4

## What is CVE-2016-0957?

CVE-2016-0957 is a high-severity vulnerability in Adobe Experience Manager, published on 10 Feb 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dispatcher before 4.1.5 in Adobe Experience Manager 5.6.1, 6.0.0, and 6.1.0 does not properly implement a URL filter, which allows remote attackers to bypass dispatcher rules via unspecified vectors.

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

It affects 2 products.


Products: Adobe Dispatcher, Adobe Experience Manager.

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

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

## Is CVE-2016-0957 being exploited?

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

Public exploit code:

- Adobe AEM Dispatcher <4.15 - Rules Bypass (nuclei): http/cves/2016/CVE-2016-0957.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2016-0957 is a high-severity vulnerability in Adobe Experience Manager, published on 10 Feb 2016. 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-2016-0957 exists.

Affected product: Adobe Experience Manager. 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-0957/ (Markdown: https://insights.sbomify.com/CVE-2016-0957/index.md)
```

## Sources

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

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