# CVE-2016-4469: Cross-site request forgery in n/a

> Remote attackers can hijack administrator sessions to modify repository configurations and upload artifacts in Apache Archiva.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Jul 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hjp8-8h3r-gwg6

## What is CVE-2016-4469?

CVE-2016-4469 is a high-severity vulnerability in n/a, published on 28 Jul 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities in Apache Archiva 1.3.9 and earlier allow remote attackers to hijack the authentication of administrators for requests that (1) add new repository proxy connectors via the token parameter to admin/addProxyConnector_commit.action, (2) new repositories via the token parameter to admin/addRepository_commit.action, (3) edit existing repositories via the token parameter to admin/editRepository_commit.action, (4) add legacy artifact paths via the token parameter to admin/addLegacyArtifactPath_commit.action, (5) change the organizational appearance via the token parameter to admin/saveAppearance.action, or (6) upload new artifacts via the token parameter to upload_submit.action.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Apache Archiva.

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

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

## Is CVE-2016-4469 being exploited?

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

Public exploit code:

- Apache Archiva 1.3.9 - Multiple Cross-Site Request Forgery Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-2251](https://insights.sbomify.com/CVE-2013-2251/): Apache Struts Improper Input Validation (critical 9.8, exploited in the wild)
- [CVE-2017-5657](https://insights.sbomify.com/CVE-2017-5657/): Apache Archiva vulnerable to Cross Site Request Forgery (high 8.0)
- [CVE-2024-27138](https://insights.sbomify.com/CVE-2024-27138/): Apache Archiva: disabling user registration is not effective (high 7.5)
- [CVE-2024-27139](https://insights.sbomify.com/CVE-2024-27139/): Apache Archiva: incorrect authentication potentially leading to account takeover (high 7.5)
- [CVE-2022-40308](https://insights.sbomify.com/CVE-2022-40308/): Apache Archiva prior to 2.2.9 may allow the anonymous user to read arbitrary files (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-4469 is a high-severity vulnerability in n/a, published on 28 Jul 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-4469 in the wild and no public exploit code.

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

## Sources

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

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