# CVE-2014-3453: Code injection in n/a

> Remote authenticated administrators can execute arbitrary PHP code via the Flag import feature in the Drupal Flag module.

- **Severity:** Medium 6.5 (`AV:N/AC:L/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:** 17 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7px2-x6xv-5jgf

## What is CVE-2014-3453?

CVE-2014-3453 is a medium-severity code injection vulnerability in n/a, published on 17 May 2014. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Eval injection vulnerability in the flag_import_form_validate function in includes/flag.export.inc in the Flag module 7.x-3.0, 7.x-3.5, and earlier for Drupal allows remote authenticated administrators to execute arbitrary PHP code via the "Flag import code" text area to admin/structure/flags/import.  NOTE: this issue could also be exploited by other attackers if the administrator ignores a security warning on the permissions assignment page.

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

## Which versions are affected by CVE-2014-3453?

It affects 1 product.


Products: Flag Module Project Flag.

## How do I fix CVE-2014-3453?

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

## Is CVE-2014-3453 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-14556](https://insights.sbomify.com/CVE-2025-14556/): XSS in Drupal 7 Flag Module (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-3453 and fix it if it is affected.

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

## Sources

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

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