# CVE-2017-8930: Cross-site request forgery in n/a

> Remote attackers can hijack admin sessions to create accounts or modify settings, leading to full application takeover.

- **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:** 14 May 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-425m-4v5p-2xch

## What is CVE-2017-8930?

CVE-2017-8930 is a high-severity vulnerability in n/a, published on 14 May 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

Multiple cross-site request forgery (CSRF) vulnerabilities in Simple Invoices 2013.1.beta.8 allow remote attackers to hijack the authentication of admins for requests that can (1) create new administrator user accounts and take over the entire application, (2) create regular user accounts, or (3) change configuration parameters such as tax rates and the enable/disable status of PayPal payment modules.

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

## Which versions are affected by CVE-2017-8930?

It affects 1 product.


Products: Simpleinvoices Simple Invoices.

## How do I fix CVE-2017-8930?

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

## Is CVE-2017-8930 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8930 and fix it if it is affected.

What it is: CVE-2017-8930 is a high-severity vulnerability in n/a, published on 14 May 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: There is no known exploitation of CVE-2017-8930 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-2017-8930/ (Markdown: https://insights.sbomify.com/CVE-2017-8930/index.md)
```

## Sources

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

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