# CVE-2018-8908: Cross-site request forgery in n/a

> Attackers can trick admins into creating malicious admin accounts via CSRF in Frog CMS user addition functionality.

- **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:** 31 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5733-3xh5-v4mq

## What is CVE-2018-8908?

CVE-2018-8908 is a high-severity vulnerability in n/a, published on 31 Mar 2018. 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

An issue was discovered in /admin/?/user/add in Frog CMS 0.9.5. The application's add user functionality suffers from CSRF. A malicious user can craft an HTML page and use it to trick a victim into clicking on it; once executed, a malicious user will be created with admin privileges. This happens due to lack of an anti-CSRF token in state modification requests.

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

## Which versions are affected by CVE-2018-8908?

It affects 1 product.


Products: Frog Cms Project Frog Cms.

## How do I fix CVE-2018-8908?

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

## Is CVE-2018-8908 being exploited?

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

Public exploit code:

- Frog CMS 0.9.5 - Cross-Site Request Forgery (Add User) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-4912](https://insights.sbomify.com/CVE-2014-4912/): File upload in n/a (critical 9.8)
- [CVE-2018-20776](https://insights.sbomify.com/CVE-2018-20776/): Information disclosure in n/a (high 7.5)
- [CVE-2018-20772](https://insights.sbomify.com/CVE-2018-20772/): Code injection in n/a (high 7.2)
- [CVE-2018-20773](https://insights.sbomify.com/CVE-2018-20773/): Code injection in n/a (high 7.2)
- [CVE-2018-20775](https://insights.sbomify.com/CVE-2018-20775/): Code injection in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-8908 and fix it if it is affected.

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

## Sources

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

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