Read the docs
TI-2022-01708 Aliases CVE-2022-1844GHSA-rr2m-mr88-9j4f

WP Sentry <= 1.0 - Arbitrary Settings Update to Stored XSS via CSRF

Priority LOW 20CWE-352Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Required
Attack complexity
Low
Impact type
Tampering
Confidentiality · integrity · availability
None · Low · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-352.

Summary

The WP Sentry WordPress plugin through 1.0 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack and lead to Stored Cross-Site Scripting due to the lack of sanitisation and escaping as well

Why it matters now

EPSS 0.00429 37th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by NVD
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
UnknownWP Sentry1.0 – 1.0—No fix listedCNA
  • WP Sentry VendorUnknown Affected 1.0 – 1.0 Fixed in — No fix listed CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:wp-sentry_project:wp-sentry:*:*:*:*:*:wordpress:*:*up to 1.0VulnerableWp-sentry Project
  • cpe:2.3:a:wp-sentry_project:wp-sentry:*:*:*:*:*:wordpress:*:* Versions up to 1.0 Vulnerable ·Wp-sentry Project

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2022-1844
  2. 2026-10-03 Alias added: GHSA-rr2m-mr88-9j4f

References

Sources