CVE-2022-0503: The WordPress Multisite Content Copier/Updater WordPress plugin before 2.1.2 does not sanitise and escape the

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

multisite content copier\/updater: upgrade to 2.1.2. Exact commands for each OS are on this page.

Q: Is CVE-2022-0503 being exploited?

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

CVE-2022-0503 affects multisite content copier\/updater. Severity is medium (CVSS 6.1). The WordPress Multisite Content Copier/Updater WordPress plugin before 2.1.2 does not sanitise and escape the s parameter before outputting it back in an attribute, leading to a Reflected Cross-Site Scripting issue in the network dashboard

Q: How urgent is CVE-2022-0503?

Priority 40/100. Public exploit reference

This month

MEDIUM 6.1UPGRADE

CVE-2022-0503 is a medium-severity flaw (CVSS 6.1) affecting multisite content copier\/updater. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The WordPress Multisite Content Copier/Updater WordPress plugin before 2.1.2 does not sanitise and escape the s parameter before outputting it back in an attribute, leading to a Reflected Cross-Site Scripting issue in the network dashboard

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-03-14
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: obtaininfotech

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

Am I affected?

Timeline

2022-03-14 15:15 UTCPublished CVE record published
2026-06-17 04:20 UTCUpdated Record last modified

obtaininfotech multisite content copier\/updater UPGRADE

Affected: < 2.1.2

Fixed in: 2.1.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy multisite-content-copierupdater || rpm -q multisite-content-copierupdater || multisite-content-copierupdater --version

2. UPGRADE to 2.1.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade multisite-content-copierupdater

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade multisite-content-copierupdater

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

multisite content copier\/updater: upgrade to 2.1.2. Exact commands for each OS are on this page.

Is CVE-2022-0503 being exploited?

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

CVE-2022-0503 affects multisite content copier\/updater. Severity is medium (CVSS 6.1). The WordPress Multisite Content Copier/Updater WordPress plugin before 2.1.2 does not sanitise and escape the s parameter before outputting it back in an attribute, leading to a Reflected Cross-Site Scripting issue in the network dashboard

How urgent is CVE-2022-0503?

Priority 40/100. Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs