# CVE-2007-1180: Cross-site request forgery in n/a

> WebAPP fails to validate referrers in forms, allowing remote attackers to perform cross-site request forgery attacks against users.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **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 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-952m-9hj5-66gj

## What is CVE-2007-1180?

CVE-2007-1180 is a medium-severity vulnerability in n/a, published on 28 Feb 2007. 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

WebAPP before 0.9.9.5 does not check referrers in certain forms, which might facilitate remote cross-site request forgery (CSRF) attacks or have other unknown impact.

## Which versions are affected by CVE-2007-1180?

It affects 1 product.


Products: Web-App.org Webapp.

## How do I fix CVE-2007-1180?

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

## Is CVE-2007-1180 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-0927](https://insights.sbomify.com/CVE-2005-0927/): Other in n/a (critical 10.0)
- [CVE-2007-3419](https://insights.sbomify.com/CVE-2007-3419/): Missing authorization in n/a (high 7.5)
- [CVE-2007-3420](https://insights.sbomify.com/CVE-2007-3420/): Information disclosure in n/a (high 7.5)
- [CVE-2007-3421](https://insights.sbomify.com/CVE-2007-3421/): Missing authorization in n/a (high 7.5)
- [CVE-2007-3422](https://insights.sbomify.com/CVE-2007-3422/): Other in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1180 and fix it if it is affected.

What it is: CVE-2007-1180 is a medium-severity vulnerability in n/a, published on 28 Feb 2007. 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-2007-1180 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-2007-1180/ (Markdown: https://insights.sbomify.com/CVE-2007-1180/index.md)
```

## Sources

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

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