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

> Remote attackers can execute arbitrary PHP code in EC-CUBE via crafted input, potentially compromising the web server.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** 29 Jun 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-w79g-rg56-5hxw

## What is CVE-2013-3651?

CVE-2013-3651 is a high-severity code injection vulnerability in n/a, published on 29 Jun 2013. It can be exploited over the network.

### Official description

LOCKON EC-CUBE 2.11.2 through 2.12.4 allows remote attackers to conduct unspecified PHP code-injection attacks via a crafted string, related to data/class/SC_CheckError.php and data/class/SC_FormParam.php.

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

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

It affects 1 product.


Products: Lockon Ec-Cube.

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

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

## Is CVE-2013-3651 being exploited?

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

Public exploit code:

- CVE-2013-3651 PoC - EC-CUBE 2 (github_poc): https://github.com/motikan2010/CVE-2013-3651

## Other vulnerabilities in n/a

- [CVE-2014-0808](https://insights.sbomify.com/CVE-2014-0808/): EC-CUBE vulnerable to authorization bypass (critical 9.1)
- [CVE-2016-1201](https://insights.sbomify.com/CVE-2016-1201/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-0564](https://insights.sbomify.com/CVE-2018-0564/): Other in EC-CUBE (high 8.1)
- [CVE-2011-3988](https://insights.sbomify.com/CVE-2011-3988/): SQL injection in n/a (high 7.5)
- [CVE-2013-5993](https://insights.sbomify.com/CVE-2013-5993/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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