# CVE-2019-8421: SQL injection in n/a

> SQL injection in BageCMS allows attackers to manipulate database queries via title parameters, potentially exposing or altering data.

- **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:** 17 Feb 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6xf5-j3w7-8rqx

## What is CVE-2019-8421?

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

### Official description

upload/protected/modules/admini/views/post/index.php in BageCMS through 3.1.4 allows SQL Injection via the title or titleAlias parameter.

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

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

It affects 1 product.


Products: Bagesoft Bagecms.

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

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

## Is CVE-2019-8421 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-18258](https://insights.sbomify.com/CVE-2018-18258/): Code injection in n/a (critical 9.8)
- [CVE-2018-19560](https://insights.sbomify.com/CVE-2018-19560/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-19104](https://insights.sbomify.com/CVE-2018-19104/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-14582](https://insights.sbomify.com/CVE-2018-14582/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-18257](https://insights.sbomify.com/CVE-2018-18257/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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