CVE-2022-1063: The Thank Me Later WordPress plugin through 3.3.4 does not sanitise and escape the Message Subject field befor

Q: How do I fix CVE-2022-1063?

thank me later: upgrade to newer than 3.3.4. Exact commands for each OS are on this page.

Q: Is CVE-2022-1063 being exploited?

CVE-2022-1063 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-2022-1063 affect?

CVE-2022-1063 affects thank me later. Severity is medium (CVSS 4.8). The Thank Me Later WordPress plugin through 3.3.4 does not sanitise and escape the Message Subject field before outputting it in the Messages list, which could allow high privileges users such as admin to perform Cross-Site Scripting attack

Q: How urgent is CVE-2022-1063?

Priority 34/100. Public exploit reference

Routine

MEDIUM 4.8UPGRADE

CVE-2022-1063 is a medium-severity flaw (CVSS 4.8) affecting thank me later. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Thank Me Later WordPress plugin through 3.3.4 does not sanitise and escape the Message Subject field before outputting it in the Messages list, which could allow high privileges users such as admin to perform Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed

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 51%)
CISA exploited list	No
Weakness	CWE-79
Published	2022-04-18
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: thank me later project

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

Am I affected?

Timeline

2022-04-18 18:15 UTCPublished CVE record published
2026-06-17 04:21 UTCUpdated Record last modified

thank me later project thank me later UPGRADE

Affected: <= 3.3.4

Fixed in: newer than 3.3.4

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy thank-me-later || rpm -q thank-me-later || thank-me-later --version

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

sudo apt update && sudo apt install --only-upgrade thank-me-later

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade thank-me-later

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-2022-1063?

thank me later: upgrade to newer than 3.3.4. Exact commands for each OS are on this page.

Is CVE-2022-1063 being exploited?

CVE-2022-1063 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-2022-1063 affect?

CVE-2022-1063 affects thank me later. Severity is medium (CVSS 4.8). The Thank Me Later WordPress plugin through 3.3.4 does not sanitise and escape the Message Subject field before outputting it in the Messages list, which could allow high privileges users such as admin to perform Cross-Site Scripting attack

How urgent is CVE-2022-1063?

Priority 34/100. Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs