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

> A Cross-Site Request Forgery vulnerability in the member email editing feature allows attackers to modify user data without consent.

- **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:** 6 Dec 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-w42h-5x65-2vpx

## What is CVE-2018-19923?

CVE-2018-19923 is a high-severity vulnerability in n/a, published on 6 Dec 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 Sales & Company Management System (SCMS) through 2018-06-06. There is member/member_email.php?action=edit CSRF.

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

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

It affects 1 product.


Products: Sales \& Company Management System Project Sales \& Company Management System.

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

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

## Is CVE-2018-19923 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-19925](https://insights.sbomify.com/CVE-2018-19925/): SQL injection in n/a (critical 9.8)
- [CVE-2018-19654](https://insights.sbomify.com/CVE-2018-19654/): Business logic in n/a (high 7.5)
- [CVE-2018-19924](https://insights.sbomify.com/CVE-2018-19924/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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