# CVE-2019-8347: Cross-site request forgery in n/a

> Attackers can trick admins into adding arbitrary VIP accounts, leading to privilege escalation and data modification in BEESCMS.

- **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:** 15 Feb 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-f8jr-6jvq-67xq

## What is CVE-2019-8347?

CVE-2019-8347 is a high-severity vulnerability in n/a, published on 15 Feb 2019. 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

BEESCMS 4.0 has a CSRF vulnerability to add arbitrary VIP accounts via the admin/admin_member.php?action=add&nav=add_web_user&admin_p_nav=user URI.

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

## Which versions are affected by CVE-2019-8347?

It affects 1 product.


Products: Beescms Beescms.

## How do I fix CVE-2019-8347?

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

## Is CVE-2019-8347 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-31011](https://insights.sbomify.com/CVE-2024-31011/): File upload in n/a (critical 9.8)
- [CVE-2020-23572](https://insights.sbomify.com/CVE-2020-23572/): File upload in n/a (high 8.8)
- [CVE-2018-12739](https://insights.sbomify.com/CVE-2018-12739/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-10266](https://insights.sbomify.com/CVE-2018-10266/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2020-22334](https://insights.sbomify.com/CVE-2020-22334/): Cross-site request forgery in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-8347 and fix it if it is affected.

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

## Sources

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

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