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

> Remote attackers can hijack administrator authentication via CSRF in the admin interface, requiring an upgrade to secure the system.

- **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:** Yes
- **Published:** 2 Sep 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8p5c-w6j3-96pw

## What is CVE-2016-7123?

CVE-2016-7123 is a high-severity vulnerability in n/a, published on 2 Sep 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

Cross-site request forgery (CSRF) vulnerability in the admin web interface in GNU Mailman before 2.1.15 allows remote attackers to hijack the authentication of administrators.

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

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

It affects 1 product.


Products: Gnu Mailman.

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

Upgrade to a fixed version.

## Is CVE-2016-7123 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-6893](https://insights.sbomify.com/CVE-2016-6893/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2005-4153](https://insights.sbomify.com/CVE-2005-4153/): Denial of service in n/a (high 7.8)
- [CVE-2006-2191](https://insights.sbomify.com/CVE-2006-2191/): Other in n/a (high 7.5)
- [CVE-2004-1143](https://insights.sbomify.com/CVE-2004-1143/): Weak cryptography in n/a (high 7.5)
- [CVE-2002-0855](https://insights.sbomify.com/CVE-2002-0855/): Cross-site scripting in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-7123 is a high-severity vulnerability in n/a, published on 2 Sep 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-7123 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-7123/ (Markdown: https://insights.sbomify.com/CVE-2016-7123/index.md)
```

## Sources

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

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