# CVE-2013-4446: Code injection in n/a

> Remote attackers can execute arbitrary PHP code in the Drupal Context module when using older PHP versions without native JSON support.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 7 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2gjj-736q-7356

## What is CVE-2013-4446?

CVE-2013-4446 is a medium-severity code injection vulnerability in n/a, published on 7 Dec 2013. It can be exploited over the network.

### Official description

The _json_decode function in plugins/context_reaction_block.inc in the Context module 6.x-2.x before 6.x-3.2 and 7.x-3.x before 7.x-3.0 for Drupal, when using a version of PHP that does not support the json_decode function, allows remote attackers to execute arbitrary PHP code via unspecified vectors related to Ajax operations, possibly involving eval injection.

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

## Which versions are affected by CVE-2013-4446?

It affects 1 product.


Products: Steven Jones Context.

## How do I fix CVE-2013-4446?

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

## Is CVE-2013-4446 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-5655](https://insights.sbomify.com/CVE-2012-5655/): Missing authorization in n/a (medium 5.0)
- [CVE-2013-4445](https://insights.sbomify.com/CVE-2013-4445/): Auth bypass in n/a (medium 4.9)
- [CVE-2010-1584](https://insights.sbomify.com/CVE-2010-1584/): Cross-site scripting in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4446 and fix it if it is affected.

What it is: CVE-2013-4446 is a medium-severity code injection vulnerability in n/a, published on 7 Dec 2013. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2013-4446 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-2013-4446/ (Markdown: https://insights.sbomify.com/CVE-2013-4446/index.md)
```

## Sources

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

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