# CVE-2022-1557: ULeak Security & Monitoring <= 1.2.3 - Subscriber+ Stored Cross-Site Scripting

> Authenticated subscribers can inject malicious scripts via plugin settings, leading to stored XSS attacks against administrators.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-jc88-pjw2-xprh

## What is CVE-2022-1557?

CVE-2022-1557 is a medium-severity cross-site scripting vulnerability in Unknown ULeak Security & Monitoring Plugin, published on 16 May 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The ULeak Security & Monitoring WordPress plugin through 1.2.3 does not have authorisation and CSRF checks when updating its settings, and is also lacking sanitisation as well as escaping in some of them, which could allow any authenticated users such as subscriber to perform Stored Cross-Site Scripting attacks against admins viewing the settings

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

## Which versions are affected by CVE-2022-1557?

It affects 1 product.


Products: Uleak-Security-Dashboard Project Uleak-Security-Dashboard.

## How do I fix CVE-2022-1557?

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

## Is CVE-2022-1557 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1557 and fix it if it is affected.

What it is: CVE-2022-1557 is a medium-severity cross-site scripting vulnerability in Unknown ULeak Security & Monitoring Plugin, published on 16 May 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-1557 in the wild and no public exploit code.

Affected product: Unknown ULeak Security & Monitoring Plugin. 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-2022-1557/ (Markdown: https://insights.sbomify.com/CVE-2022-1557/index.md)
```

## Sources

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

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