CVE-2021-24619: The Per page add to head WordPress plugin through 1.4.4 does not properly sanitise one of its setting, allowin

Q: How do I fix CVE-2021-24619?

per page add to head: upgrade to newer than 1.4.4. Exact commands for each OS are on this page.

Q: Is CVE-2021-24619 being exploited?

CVE-2021-24619 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-2021-24619 affect?

CVE-2021-24619 affects per page add to head. Severity is medium (CVSS 4.8). 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 t

Q: How urgent is CVE-2021-24619?

Priority 34/100. Public exploit reference

Routine

MEDIUM 4.8UPGRADE

CVE-2021-24619 is a medium-severity flaw (CVSS 4.8) affecting per page add to head. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

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.6% (top 50%)
CISA exploited list	No
Weakness	CWE-79
Published	2021-09-13
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: evona

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

Am I affected?

Timeline

2021-09-13 18:15 UTCPublished CVE record published
2026-06-17 03:40 UTCUpdated Record last modified

evona per page add to head UPGRADE

Affected: <= 1.4.4

Fixed in: newer than 1.4.4

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy per-page-add-to-head || rpm -q per-page-add-to-head || per-page-add-to-head --version

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

sudo apt update && sudo apt install --only-upgrade per-page-add-to-head

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade per-page-add-to-head

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-2021-24619?

per page add to head: upgrade to newer than 1.4.4. Exact commands for each OS are on this page.

Is CVE-2021-24619 being exploited?

CVE-2021-24619 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-2021-24619 affect?

CVE-2021-24619 affects per page add to head. Severity is medium (CVSS 4.8). 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 t

How urgent is CVE-2021-24619?

Priority 34/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2021-24586 MEDIUM 4.3 UPGRADE The Per page add to head WordPress plugin before 1.4.4 is lacking any CSRF check when saving its settings, whi

References

← Back to latest CVEs