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

> Attackers can hijack admin sessions via CSRF to execute XML validation, potentially leading to arbitrary code execution when combined with another vulnerability.

- **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:** 18 Jan 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-7980, GHSA-7w5f-5r8v-pff6, UBUNTU-CVE-2016-7980

## What is CVE-2016-7980?

CVE-2016-7980 is a high-severity vulnerability in Spip Spip, published on 18 Jan 2017. 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 ecrire/exec/valider_xml.php in SPIP 3.1.2 and earlier allows remote attackers to hijack the authentication of administrators for requests that execute the XML validator on a local file via a crafted valider_xml request.  NOTE: this issue can be combined with CVE-2016-7998 to execute arbitrary PHP code.

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

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

It affects 1 product.


Products: Spip Spip.

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

Upgrade to a fixed version.

## Is CVE-2016-7980 being exploited?

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

Public exploit code:

- SPIP 3.1.2 - Cross-Site Request Forgery (exploitdb)

## Other vulnerabilities in Spip Spip

- [CVE-2012-4331](https://insights.sbomify.com/CVE-2012-4331/): Other in n/a (critical 10.0)
- [CVE-2008-5812](https://insights.sbomify.com/CVE-2008-5812/): Other in n/a (critical 10.0)
- [CVE-2024-8517](https://insights.sbomify.com/CVE-2024-8517/): SPIP Bigup Multipart File Upload OS Command Injection (critical 9.8)
- [CVE-2023-24258](https://insights.sbomify.com/CVE-2023-24258/): SQL injection in n/a (critical 9.8)
- [CVE-2017-9736](https://insights.sbomify.com/CVE-2017-9736/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-7980 is a high-severity vulnerability in Spip Spip, published on 18 Jan 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-7980 exists.

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

## Sources

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

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