CVE-2021-24838: The AnyComment WordPress plugin before 0.3.5 has an API endpoint which passes user input via the redirect para

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

anycomment: upgrade to 0.3.5. Exact commands for each OS are on this page.

Q: Is CVE-2021-24838 being exploited?

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

CVE-2021-24838 affects anycomment. Severity is medium (CVSS 6.1). The AnyComment WordPress plugin before 0.3.5 has an API endpoint which passes user input via the redirect parameter to the wp_redirect() function without being validated first, leading to an Open Redirect issue, which according to the vendo

Q: How urgent is CVE-2021-24838?

Priority 47/100. Public exploit reference

This month

MEDIUM 6.1UPGRADE

CVE-2021-24838 is a medium-severity flaw (CVSS 6.1) affecting anycomment. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The AnyComment WordPress plugin before 0.3.5 has an API endpoint which passes user input via the redirect parameter to the wp_redirect() function without being validated first, leading to an Open Redirect issue, which according to the vendor, is a feature.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	2.2% (top 17%)
CISA exploited list	No
Weakness	CWE-601
Published	2022-01-17
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: bologer

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

Am I affected?

Timeline

2022-01-17 13:15 UTCPublished CVE record published
2026-06-17 03:40 UTCUpdated Record last modified

bologer anycomment UPGRADE

Affected: < 0.3.5

Fixed in: 0.3.5

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy anycomment || rpm -q anycomment || anycomment --version

2. UPGRADE to 0.3.5 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade anycomment

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade anycomment

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Nuclei scan template: WordPress AnyComment <0.3.5 - Open Redirect

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

anycomment: upgrade to 0.3.5. Exact commands for each OS are on this page.

Is CVE-2021-24838 being exploited?

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

CVE-2021-24838 affects anycomment. Severity is medium (CVSS 6.1). The AnyComment WordPress plugin before 0.3.5 has an API endpoint which passes user input via the redirect parameter to the wp_redirect() function without being validated first, leading to an Open Redirect issue, which according to the vendo

How urgent is CVE-2021-24838?

Priority 47/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2022-0279 LOW 3.1 UPGRADE The AnyComment WordPress plugin before 0.2.18 is affected by a race condition when liking/disliking a comment/
CVE-2022-0134 HIGH 8.8 UPGRADE The AnyComment WordPress plugin before 0.2.18 does not have CSRF checks in the Import and Revert HyperComments

References

← Back to latest CVEs