# Apache Archiva does not require entry of the administrator's password at the time of modifying a user account

Advisory record · `GHSA-5p54-jj38-3hxj`

- **Identifiers:** `GHSA-5p54-jj38-3hxj` · `CVE-2010-4408`
- **State:** Confirmed
- **Severity:** CVSS 4.0, no score published
- **Critical:** No
- **Weakness (CWE):** [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 14 May 2022
- **Updated:** 12 Apr 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 May 2022, 02:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.apache.archiva:archiva` (Maven): affected `>=1.0, <1.3.2`; fixed in `1.3.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache Archiva versions 1.0 through 1.0.3, 1.1 through 1.1.4, 1.2 through 1.2.2, and 1.3 through 1.3.1 do not require the administrator's password when modifying a user account. An attacker with access to an unattended administrator workstation, or one who can exploit a cross-site request forgery flaw, can use this to gain privileges. Upgrade to Apache Archiva 1.3.2, which fixes the issue.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- Score not published, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.020, the 80th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:11 UTC: First seen by agentprime
- 31 Oct 2026, 15:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-5p54-jj38-3hxj)

## Sources

- [GitHub Advisory Database: GHSA-5p54-jj38-3hxj](https://github.com/advisories/GHSA-5p54-jj38-3hxj)
- [OSV: GHSA-5p54-jj38-3hxj](https://osv.dev/vulnerability/GHSA-5p54-jj38-3hxj)
- <https://nvd.nist.gov/vuln/detail/CVE-2010-4408>
- <https://github.com/apache/archiva>
- <https://web.archive.org/web/20201209001124/http://www.securityfocus.com/archive/1/514937/100/0/threaded>
- <http://archiva.apache.org/security.html>
- <http://mail-archives.apache.org/mod_mbox/archiva-users/201011.mbox/ajax/%3CAANLkTimXejHAuXdoUKLN=GkNty1_XnRCbv0YA0T2cS_2%40mail.gmail.com%3E>
- <http://mail-archives.apache.org/mod_mbox/archiva-users/201011.mbox/ajax/%3CAANLkTimXejHAuXdoUKLN=GkNty1_XnRCbv0YA0T2cS_2@mail.gmail.com%3E>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-5p54-jj38-3hxj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-5p54-jj38-3hxj/>. Everything for agents: <https://agentprime.io/llms.txt>.
