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

> Remote attackers can execute arbitrary PHP code by injecting malicious input into the site name configuration field in baigoSSO.

- **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:** 24 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-v2p2-mj8c-jjfr

## What is CVE-2019-10015?

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

### Official description

baigoStudio baigoSSO v3.0.1 allows remote attackers to execute arbitrary PHP code via the first form field of a configuration screen, because this code is written to the BG_SITE_NAME field in the opt_base.inc.php file.

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

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

It affects 1 product.


Products: Baigo Baigo Sso.

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

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

## Is CVE-2019-10015 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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