# CVE-2015-5643: Code injection in n/a

> Remote attackers can execute arbitrary PHP code due to improper database configuration in the installer.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Oct 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2mj3-mc6h-qcgc

## What is CVE-2015-5643?

CVE-2015-5643 is a medium-severity code injection vulnerability in n/a, published on 3 Oct 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The installer in ICZ MATCHA INVOICE before 2.5.7 does not properly configure the database, which allows remote attackers to execute arbitrary PHP code via unspecified vectors.

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

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

It affects 1 product.


Products: Icz Matchasns.

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

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

## Is CVE-2015-5643 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-5644](https://insights.sbomify.com/CVE-2015-5644/): Code injection in n/a (medium 6.8)
- [CVE-2015-5642](https://insights.sbomify.com/CVE-2015-5642/): SQL injection in n/a (medium 6.5)
- [CVE-2015-5645](https://insights.sbomify.com/CVE-2015-5645/): ICZ MATCHA SNS before 1.3.7 allows remote authenticated users to obtain administrative privileges via unspecified vectors. (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-5643 is a medium-severity code injection vulnerability in n/a, published on 3 Oct 2015. 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-5643 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-2015-5643/ (Markdown: https://insights.sbomify.com/CVE-2015-5643/index.md)
```

## Sources

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

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