Pagebar < 2.70 - Arbitrary Settings Update via CSRF to Stored XSS

published 2022-07-11 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-25038

cvss: 5.4; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits: 0; none known

The pagebar WordPress plugin before 2.70 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. Furthermore, due to the lack of sanitisation in some of them, it could also lead to Stored XSS issues

Patch / fix

fixed in 1

pagebar_project pagebar 2.70

Exploit prediction

0.34% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

wpscan.com https://wpscan.com/vulnerability/e648633e-868b-45b2-870a-308a2f9cb7f5 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	5.4	CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
NVD	2.0	3.5	AV:N/AC:M/Au:S/C:N/I:P/A:N

Affected products

Unknown pagebar

Classification

Weakness

CWE-352 Cross-Site Request Forgery
CWE-79 Improper Neutralization of Input During Web Page Generation

Technology feeds

WordPress rss critical rss

References

wpscan.com /vulnerability/e648633e-868b-45b2-870a-308a2f9cb7f5
exploit, third-party-advisory

Sources

CVE List CVE-2022-1757
NVD CVE-2022-1757

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary