# CVE-2015-3933: MetalGenix GeniXCMS vulnerable to SQL Injection

> Remote attackers can execute arbitrary SQL commands via email or userid parameters in GeniXCMS registration, potentially compromising database integrity.

- **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:** 8 Nov 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-q4hw-62mx-q37w

## What is CVE-2015-3933?

CVE-2015-3933 is a critical SQL injection vulnerability in n/a, published on 8 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in inc/lib/User.class.php in MetalGenix GeniXCMS before 0.0.3-patch allow remote attackers to execute arbitrary SQL commands via the (1) email parameter or (2) userid parameter to register.php.

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

## Which versions are affected by CVE-2015-3933?

2 open source packages ship an affected version, including genix/cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `genix/cms` | Packagist | All versions to 0.0.3 | None |
| `genix/cms` | Packagist | All versions to 0.0.3 | None |

Products: Metalgenix Genixcms.

## How do I fix CVE-2015-3933?

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

## Is CVE-2015-3933 being exploited?

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

Public exploit code:

- GeniXCMS 0.0.3 - 'register.php' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-5959](https://insights.sbomify.com/CVE-2017-5959/): Cross-site request forgery in n/a (critical 9.8)
- [CVE-2017-5574](https://insights.sbomify.com/CVE-2017-5574/): SQL injection in n/a (critical 9.8)
- [CVE-2017-5575](https://insights.sbomify.com/CVE-2017-5575/): SQL injection in n/a (critical 9.8)
- [CVE-2017-5517](https://insights.sbomify.com/CVE-2017-5517/): SQL injection in n/a (critical 9.8)
- [CVE-2017-5519](https://insights.sbomify.com/CVE-2017-5519/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-3933 and fix it if it is affected.

What it is: CVE-2015-3933 is a critical SQL injection vulnerability in n/a, published on 8 Nov 2017. 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-2015-3933 in the wild and no public exploit code.

Affected packages and fixed versions:
- genix/cms (Packagist): affected all versions up to 0.0.3; no fix listed
- genix/cms (Packagist): affected all versions up to 0.0.3; no fix listed

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-2015-3933/ (Markdown: https://insights.sbomify.com/CVE-2015-3933/index.md)
```

## Sources

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

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