# CVE-2014-4526: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML via parameters in the efence WordPress plugin, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wwrq-c42j-whw3

## What is CVE-2014-4526?

CVE-2014-4526 is a medium-severity cross-site scripting vulnerability in n/a, published on 2 Jul 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in callback.php in the efence plugin 1.3.2 and earlier for WordPress allow remote attackers to inject arbitrary web script or HTML via the (1) message, (2) zoneid, (3) pubKey, or (4) privKey parameter.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Efence Project Efence.

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

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

## Is CVE-2014-4526 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-4526 is a medium-severity cross-site scripting vulnerability in n/a, published on 2 Jul 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-4526 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-4526/ (Markdown: https://insights.sbomify.com/CVE-2014-4526/index.md)
```

## Sources

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

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