# CVE-2019-16524: Cross-site scripting in n/a

> Stored XSS in Easy FancyBox WordPress plugin allows attackers to inject scripts via settings, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h6hv-v4xc-8xxh

## What is CVE-2019-16524?

CVE-2019-16524 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Sep 2019. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The easy-fancybox plugin before 1.8.18 for WordPress (aka Easy FancyBox) is susceptible to Stored XSS in the Settings Menu inc/class-easyfancybox.php due to improper encoding of arbitrarily submitted settings parameters. This occurs because there is no inline styles output filter.

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

## Which versions are affected by CVE-2019-16524?

It affects 1 product.


Products: Status301 Easy Fancybox.

## How do I fix CVE-2019-16524?

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

## Is CVE-2019-16524 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-16524 and fix it if it is affected.

What it is: CVE-2019-16524 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Sep 2019. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-16524 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-2019-16524/ (Markdown: https://insights.sbomify.com/CVE-2019-16524/index.md)
```

## Sources

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

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