# CVE-2018-19462: SQL injection in n/a

> Remote attackers can execute arbitrary PHP code via SQL injection in EmpireCMS, leading to full system compromise.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m6qm-rc68-729q

## What is CVE-2018-19462?

CVE-2018-19462 is a high-severity SQL injection vulnerability in n/a, published on 7 Jun 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

admin\db\DoSql.php in EmpireCMS through 7.5 allows remote attackers to execute arbitrary PHP code via SQL injection that uses a .php filename in a SELECT INTO OUTFILE statement to admin/admin.php.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Phome Empirecms.

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

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

## Is CVE-2018-19462 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-28585](https://insights.sbomify.com/CVE-2022-28585/): SQL injection in n/a (critical 9.8)
- [CVE-2020-22937](https://insights.sbomify.com/CVE-2020-22937/): Code injection in n/a (critical 9.8)
- [CVE-2018-20300](https://insights.sbomify.com/CVE-2018-20300/): Code injection in n/a (critical 9.8)
- [CVE-2018-18869](https://insights.sbomify.com/CVE-2018-18869/): Path traversal in n/a (critical 9.8)
- [CVE-2018-18449](https://insights.sbomify.com/CVE-2018-18449/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-19462 is a high-severity SQL injection vulnerability in n/a, published on 7 Jun 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-19462 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-19462/ (Markdown: https://insights.sbomify.com/CVE-2018-19462/index.md)
```

## Sources

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

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