The Per page add to head WordPress plugin through 1.4.4 does not properly sanitise one of its setting, allowing malicious HTML to be inserted by high privilege users even when the unfiltered_html capability is disallowed, which could lead to Cross-Site Scripting issues.
Product
wordpress per-page-add-to vulnerabilities
2 published CVES affecting wordpress per-page-add-to, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 2
- Critical
- 0
- High
- 0
- Medium
- 2
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest wordpress per-page-add-to CVEs
Newest publication first
-
MediumCVSS 4.8 EPSS 0.62%
-
MediumCVSS 4.3 EPSS 0.48%
The Per page add to head WordPress plugin before 1.4.4 is lacking any CSRF check when saving its settings, which could allow attackers to make a logged in admin change them. Furthermore, as the plugin allows arbitrary HTML to be inserted in one of the setting (feature mentioned b...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.