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

> Cross-site request forgery in PopojiCMS allows attackers to create administrative accounts by tricking users into visiting a malicious link.

- **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:** 5 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-29v9-m8r8-v85x

## What is CVE-2018-18935?

CVE-2018-18935 is a high-severity vulnerability in n/a, published on 5 Nov 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 PopojiCMS v2.0.1. It has CSRF via the po-admin/route.php?mod=component&act=addnew URI, as demonstrated by adding a level=1 account.

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

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

It affects 1 product.


Products: Popojicms Popojicms.

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

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

## Is CVE-2018-18935 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-18934](https://insights.sbomify.com/CVE-2018-18934/): File upload in n/a (critical 9.8)
- [CVE-2022-47766](https://insights.sbomify.com/CVE-2022-47766/): File upload in n/a (high 8.8)
- [CVE-2019-9549](https://insights.sbomify.com/CVE-2019-9549/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2024-58284](https://insights.sbomify.com/CVE-2024-58284/): PopojiCMS 2.0.1 Remote Command Execution via Authenticated Metadata Settings (high 8.6)
- [CVE-2018-18936](https://insights.sbomify.com/CVE-2018-18936/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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