# CVE-2019-9651: Code injection in n/a

> Insufficient filtering in SDCMS allows attackers to execute arbitrary PHP code via bypassed function and extension checks.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w635-v6rj-h657

## What is CVE-2019-9651?

CVE-2019-9651 is a critical code injection vulnerability in n/a, published on 11 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in SDCMS V1.7. In the \app\admin\controller\themecontroller.php file, the check_bad() function's filtering is not strict, resulting in PHP code execution. This occurs because some dangerous PHP functions (such as "eval") are blocked but others (such as "system") are not, and because ".php" is blocked but ".PHP" is not blocked.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Sdcms Sdcms.

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

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

## Is CVE-2019-9651 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-9652](https://insights.sbomify.com/CVE-2019-9652/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-11004](https://insights.sbomify.com/CVE-2018-11004/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-19748](https://insights.sbomify.com/CVE-2018-19748/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-9651 is a critical code injection vulnerability in n/a, published on 11 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-9651 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-9651/ (Markdown: https://insights.sbomify.com/CVE-2019-9651/index.md)
```

## Sources

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

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