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

> Authenticated users with newsletter scheduling permissions can inject PHP code that executes via cron, leading to remote code execution.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Dec 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-99mx-6v2c-6f3v

## What is CVE-2012-5537?

CVE-2012-5537 is a medium-severity code injection vulnerability in n/a, published on 3 Dec 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Simplenews Scheduler module 6.x-2.x before 6.x-2.4 for Drupal allows remote authenticated users with the "send scheduled newsletters" permission to inject arbitrary PHP code into the scheduling form, which is later executed by cron.

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

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

It affects 1 product.


Products: Simplenews Scheduler Project Simplenews Scheduler.

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

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

## Is CVE-2012-5537 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2012-5537 is a medium-severity code injection vulnerability in n/a, published on 3 Dec 2012. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-5537 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-5537/ (Markdown: https://insights.sbomify.com/CVE-2012-5537/index.md)
```

## Sources

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

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