# CVE-2014-7297: Other in n/a

> Unspecified vulnerability in the Enfold WordPress theme folder framework allows attackers to potentially compromise the site.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 13 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v6fh-f9x6-866w

## What is CVE-2014-7297?

CVE-2014-7297 is a critical vulnerability in n/a, published on 13 Oct 2014. 

### Official description

Unspecified vulnerability in the folder framework in the Enfold theme before 3.0.1 for WordPress has unknown impact and attack vectors.

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

It affects 1 product.


Products: Kriesi Enfold.

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

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

## Is CVE-2014-7297 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-37199](https://insights.sbomify.com/CVE-2024-37199/): WordPress Enfold theme <= 5.6.9 - Reflected Cross Site Scripting (XSS) vulnerability (high 7.1)
- [CVE-2023-38400](https://insights.sbomify.com/CVE-2023-38400/): WordPress Enfold Theme <= 5.6.4 is vulnerable to Cross Site Scripting (XSS) (high 7.1)
- [CVE-2024-13695](https://insights.sbomify.com/CVE-2024-13695/): Enfold <= 6.0.9 - Authenticated (Subscriber+) Server-Side Request Forgery via attachment_id (medium 6.4)
- [CVE-2024-5061](https://insights.sbomify.com/CVE-2024-5061/): Enfold <= 6.0.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via wrapper_class and class Parameters (medium 6.4)
- [CVE-2021-24719](https://insights.sbomify.com/CVE-2021-24719/): Enfold Theme < 4.8.4 - Reflected Cross-Site Scripting (XSS) (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-7297 is a critical vulnerability in n/a, published on 13 Oct 2014. 
Exploitation: There is no known exploitation of CVE-2014-7297 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-7297/ (Markdown: https://insights.sbomify.com/CVE-2014-7297/index.md)
```

## Sources

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

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