Yith Maintenance ModeWordPress extension · Yithemes
CVE-2021-36841
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAuthenticated Stored Cross-Site Scripting (XSS) vulnerability in YITH Maintenance Mode (WordPress plugin) versions <= 1.3.7, vulnerable parameter &yith_maintenance_newsletter_submit_label. Possible even when unfiltered HTML is disallowed by WordPress configuration.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAuthenticated stored XSS vulnerability in YITH Maintenance Mode plugin where the newsletter_submit_label parameter (yith_maintenance_newsletter_submit_label) does not properly sanitize user input before storing it, allowing malicious scripts to persist and execute when the maintenance mode page is rendered.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Yith Maintenance ModeWordPress extension
<= 1.3.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify YITH Maintenance Mode plugin is installedCheck your WordPress plugin directory or admin panel for Yith Maintenance Mode plugin presenceAffected if Plugin is not installed or not present in the system
-
Identify installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find Yith Maintenance Mode, or inspect the plugin header in /wp-content/plugins/yith-maintenance-mode/main.php for 'Version:' fieldAffected if Version is 1.3.7 or lower
-
Confirm plugin is activeCheck WordPress Plugins admin page - the plugin must be activated for the vulnerability to be exploitableAffected if Plugin is active and running
-
Check if maintenance mode is enabledNavigate to YITH Maintenance Mode settings in WordPress admin and verify if the maintenance mode is turned on and visible to visitorsAffected if Maintenance mode is enabled and publicly accessible
-
Inspect newsletter submit label settingGo to YITH Maintenance Mode > Settings and examine the 'Newsletter Submit Label' field for any unexpected HTML, script tags, or encoded charactersAffected if The newsletter_submit_label (yith_maintenance_newsletter_submit_label) contains unsanitized HTML or script tags
You are affected if YITH Maintenance Mode plugin version 1.3.7 or lower is installed, active, has maintenance mode enabled, and the newsletter_submit_label setting contains unsanitized user input.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate YITH Maintenance Mode plugin to version 1.3.8 or later. If immediate update is not possible, restrict administrative access to only trusted users who have legitimate need to configure the plugin settings.
Fix this in Yith Maintenance Mode
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-36841 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-36841 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data