CVE-2022-3610: The Jeeng Push Notifications WordPress plugin before 2.0.4 does not sanitise and escape some of its settings,

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

jeeng push notifications: upgrade to 2.0.4. Exact commands for each OS are on this page.

Q: Is CVE-2022-3610 being exploited?

CVE-2022-3610 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-3610 affect?

CVE-2022-3610 affects jeeng push notifications. Severity is medium (CVSS 4.8). The Jeeng Push Notifications WordPress plugin before 2.0.4 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html

Q: How urgent is CVE-2022-3610?

Priority 33/100. Public exploit reference

Routine

MEDIUM 4.8UPGRADE

CVE-2022-3610 is a medium-severity flaw (CVSS 4.8) affecting jeeng push notifications. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Jeeng Push Notifications WordPress plugin before 2.0.4 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	4.8 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	Required
EPSS exploit chance	0.5% (top 55%)
CISA exploited list	No
Published	2022-11-28
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: jeeng push notifications project

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

Am I affected?

Timeline

2022-11-28 14:15 UTCPublished CVE record published
2026-06-17 04:59 UTCUpdated Record last modified

jeeng push notifications project jeeng push notifications UPGRADE

Affected: < 2.0.4

Fixed in: 2.0.4

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy jeeng-push-notifications || rpm -q jeeng-push-notifications || jeeng-push-notifications --version

2. UPGRADE to 2.0.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade jeeng-push-notifications

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade jeeng-push-notifications

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-3610?

jeeng push notifications: upgrade to 2.0.4. Exact commands for each OS are on this page.

Is CVE-2022-3610 being exploited?

CVE-2022-3610 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-3610 affect?

CVE-2022-3610 affects jeeng push notifications. Severity is medium (CVSS 4.8). The Jeeng Push Notifications WordPress plugin before 2.0.4 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html

How urgent is CVE-2022-3610?

Priority 33/100. Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs