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

> Remote attackers can execute arbitrary PHP code in SOY CMS by injecting PHP tags into a text field, requiring immediate patching.

- **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:** 20 Apr 2019
- **Updated:** 15 Nov 2024
- **Also known as:** GHSA-gvjh-v5q9-73c3

## What is CVE-2019-11376?

CVE-2019-11376 is a high-severity code injection vulnerability in n/a, published on 20 Apr 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SOY CMS v3.0.2 allows remote attackers to execute arbitrary PHP code via a <?php substring in the second text box. NOTE: the vendor indicates that there was an assumption that the content is "made editable on its own.

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

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

It affects 1 product.


Products: Brassica Soy Cms.

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

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

## Is CVE-2019-11376 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-15188](https://insights.sbomify.com/CVE-2020-15188/): Unauthenticated Remote Code Execution in SOY CMS (critical 10.0)
- [CVE-2020-15189](https://insights.sbomify.com/CVE-2020-15189/): Remote Code Execution in SOY CMS (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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