# CVE-2012-5304: Code injection in n/a

> Remote attackers can inject arbitrary PHP code if the administrator fails to follow installation documentation recommendations.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-qv7q-gq5r-9gcx

## What is CVE-2012-5304?

CVE-2012-5304 is a high-severity code injection vulnerability in n/a, published on 6 Oct 2012. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Static code injection vulnerability in administration/install.php in YVS Image Gallery allows remote attackers to inject arbitrary PHP code into functions/db_connect.php via unspecified vectors.  NOTE: this is only a vulnerability when the administrator does not follow recommendations in the product's installation documentation.

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

## Which versions are affected by CVE-2012-5304?

It affects 1 product.


Products: Yuriy v Semenikhin Yvs Image Gallery.

## How do I fix CVE-2012-5304?

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

## Is CVE-2012-5304 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-1564](https://insights.sbomify.com/CVE-2012-1564/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-5304 and fix it if it is affected.

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

## Sources

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

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