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

> Reflected XSS in CSS Hero plugin allows attackers to execute arbitrary JavaScript, potentially stealing cookies or hijacking user sessions.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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:** 4 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3vww-prm4-rg7q

## What is CVE-2019-19133?

CVE-2019-19133 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Dec 2019. 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

The CSS Hero plugin through 4.0.3 for WordPress is prone to reflected XSS via the URI in a csshero_action=edit_page request because it fails to sufficiently sanitize user-supplied input. An attacker may leverage this issue to execute arbitrary JavaScript in the browser of an unsuspecting user in the context of the affected site. This may allow the attacker to steal cookies or launch other attacks.

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

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

It affects 1 product.


Products: Csshero Csshero.

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

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

## Is CVE-2019-19133 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-19133 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Dec 2019. 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-2019-19133 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-19133/ (Markdown: https://insights.sbomify.com/CVE-2019-19133/index.md)
```

## Sources

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

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