CVE-2022-1217: The Custom TinyMCE Shortcode Button WordPress plugin through 1.1 does not sanitise and escape the PHP_SELF var

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

custom tinymce shortcode button: upgrade to newer than 1.1. Exact commands for each OS are on this page.

Q: Is CVE-2022-1217 being exploited?

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

CVE-2022-1217 affects custom tinymce shortcode button. Severity is medium (CVSS 6.1). The Custom TinyMCE Shortcode Button WordPress plugin through 1.1 does not sanitise and escape the PHP_SELF variable before outputting it back in an attribute in an admin page, leading to Reflected Cross-Site Scripting.

Q: How urgent is CVE-2022-1217?

Priority 40/100. Public exploit reference

This month

MEDIUM 6.1UPGRADE

CVE-2022-1217 is a medium-severity flaw (CVSS 6.1) affecting custom tinymce shortcode button. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Custom TinyMCE Shortcode Button WordPress plugin through 1.1 does not sanitise and escape the PHP_SELF variable before outputting it back in an attribute in an admin page, leading to Reflected Cross-Site Scripting.

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	0.8% (top 43%)
CISA exploited list	No
Weakness	CWE-79
Published	2022-05-16
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: custom tinymce shortcode button project

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

Am I affected?

Timeline

2022-05-16 15:15 UTCPublished CVE record published
2026-06-17 04:22 UTCUpdated Record last modified

custom tinymce shortcode button project custom tinymce shortcode button UPGRADE

Affected: <= 1.1

Fixed in: newer than 1.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy custom-tinymce-shortcode-button || rpm -q custom-tinymce-shortcode-button || custom-tinymce-shortcode-button --version

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

sudo apt update && sudo apt install --only-upgrade custom-tinymce-shortcode-button

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade custom-tinymce-shortcode-button

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

custom tinymce shortcode button: upgrade to newer than 1.1. Exact commands for each OS are on this page.

Is CVE-2022-1217 being exploited?

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

CVE-2022-1217 affects custom tinymce shortcode button. Severity is medium (CVSS 6.1). The Custom TinyMCE Shortcode Button WordPress plugin through 1.1 does not sanitise and escape the PHP_SELF variable before outputting it back in an attribute in an admin page, leading to Reflected Cross-Site Scripting.

How urgent is CVE-2022-1217?

Priority 40/100. Public exploit reference

Software pages

WordPress vulnerabilities · PHP vulnerabilities

References

← Back to latest CVEs