CVE-2022-1557: The ULeak Security & Monitoring WordPress plugin through 1.2.3 does not have authorisation and CSRF checks whe

Q: How do I fix CVE-2022-1557?

uleak-security-dashboard: upgrade to newer than 1.2.3. Exact commands for each OS are on this page.

Q: Is CVE-2022-1557 being exploited?

CVE-2022-1557 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-1557 affect?

CVE-2022-1557 affects uleak-security-dashboard. Severity is medium (CVSS 5.4). 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

Q: How urgent is CVE-2022-1557?

Priority 41/100. Public exploit reference

This month

MEDIUM 5.4UPGRADE

CVE-2022-1557 is a medium-severity flaw (CVSS 5.4) affecting uleak-security-dashboard. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	1.1% (top 34%)
CISA exploited list	No
Weakness	CWE-79
Published	2022-05-16
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: uleak-security-dashboard project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-05-16 15:15 UTCPublished CVE record published
2026-06-17 04:22 UTCUpdated Record last modified

uleak-security-dashboard project uleak-security-dashboard UPGRADE

Affected: <= 1.2.3

Fixed in: newer than 1.2.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy uleak-security-dashboard || rpm -q uleak-security-dashboard || uleak-security-dashboard --version

2. UPGRADE to newer than 1.2.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade uleak-security-dashboard

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade uleak-security-dashboard

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-1557?

uleak-security-dashboard: upgrade to newer than 1.2.3. Exact commands for each OS are on this page.

Is CVE-2022-1557 being exploited?

CVE-2022-1557 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-1557 affect?

CVE-2022-1557 affects uleak-security-dashboard. Severity is medium (CVSS 5.4). 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

How urgent is CVE-2022-1557?

Priority 41/100. Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs