CVE-2021-39356: The Content Staging WordPress plugin is vulnerable to Stored Cross-Site Scripting due to insufficient input va

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

content staging: upgrade to newer than 2.0.1. Exact commands for each OS are on this page.

Q: Is CVE-2021-39356 being exploited?

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

CVE-2021-39356 affects content staging. Severity is medium (CVSS 5.5). The Content Staging WordPress plugin is vulnerable to Stored Cross-Site Scripting due to insufficient input validation and escaping via several parameters that are echo'd out via the ~/templates/settings.php file which allowed attackers wit

Q: How urgent is CVE-2021-39356?

Priority 40/100. Public exploit reference

This month

MEDIUM 5.5UPGRADE

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

The Content Staging WordPress plugin is vulnerable to Stored Cross-Site Scripting due to insufficient input validation and escaping via several parameters that are echo'd out via the ~/templates/settings.php file which allowed attackers with administrative user access to inject arbitrary web scripts, in versions up to and including 2.0.1. This affects multi-site installations where unfiltered_html is disabled for administrators, and sites where u

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	1.0% (top 38%)
CISA exploited list	No
Weakness	CWE-79
Published	2021-10-21
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: content staging project

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

Am I affected?

Timeline

2021-10-21 20:15 UTCPublished CVE record published
2026-06-17 04:03 UTCUpdated Record last modified

content staging project content staging UPGRADE

Affected: <= 2.0.1

Fixed in: newer than 2.0.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy content-staging || rpm -q content-staging || content-staging --version

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

sudo apt update && sudo apt install --only-upgrade content-staging

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade content-staging

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

content staging: upgrade to newer than 2.0.1. Exact commands for each OS are on this page.

Is CVE-2021-39356 being exploited?

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

CVE-2021-39356 affects content staging. Severity is medium (CVSS 5.5). The Content Staging WordPress plugin is vulnerable to Stored Cross-Site Scripting due to insufficient input validation and escaping via several parameters that are echo'd out via the ~/templates/settings.php file which allowed attackers wit

How urgent is CVE-2021-39356?

Priority 40/100. Public exploit reference

Software pages

WordPress vulnerabilities · PHP vulnerabilities

References

← Back to latest CVEs