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

> Authenticated administrators can execute arbitrary PHP code via the Link Title field when the Title has PHP option is enabled.

- **Severity:** Medium 4.6 (`AV:N/AC:H/Au:S/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:** 3 Dec 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-x7v2-r3rp-hc39

## What is CVE-2012-6065?

CVE-2012-6065 is a medium-severity code injection vulnerability in n/a, published on 3 Dec 2012. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The OM Maximenu module 6.x-1.43 and earlier for Drupal, when the "Title has PHP" option is enabled, allows remote authenticated users with the "Administer OM Maximenu" permission to execute arbitrary PHP code via a "Link Title," a different vulnerability than CVE-2012-5553.

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

It affects 1 product.


Products: Daniel Honrade Om Maximenu.

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

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

## Is CVE-2012-6065 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-5553](https://insights.sbomify.com/CVE-2012-5553/): Cross-site scripting in n/a (low 2.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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