Maintenance SwitchWordPress extension · Fugu
CVE-2022-47590
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in Fugu Maintenance Switch plugin <= 1.5.2 versions.
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 · moderate confidenceA reflected cross-site scripting (XSS) vulnerability in the Fugu Maintenance Switch WordPress plugin versions 1.5.2 and below allows unauthenticated attackers to inject malicious JavaScript through unsanitized user input, which executes in victim's browsers when they visit crafted URLs.
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
Maintenance SwitchWordPress extension
<= 1.5.2CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Locate the installed version of Fugu Maintenance SwitchIn WordPress admin, go to Plugins > Installed Plugins and find 'Fugu Maintenance Switch' in the list. The version number is displayed below the plugin name. Alternatively, inspect the main plugin file (fugu-maintenance-switch.php) in wp-content/plugins/ and look for the 'Version' header in the file comments.Affected if The version listed is 1.5.2 or any version lower (e.g., 1.5.1, 1.5.0, 1.4.0).
-
Confirm the plugin is activeIn WordPress admin under Plugins > Installed Plugins, check whether Fugu Maintenance Switch shows as 'Active' rather than 'Inactive' or 'Must-Use'.Affected if The plugin is active on the site.
-
Check for plugin endpoint exposureIdentify the URL path where the plugin handles user input. This is typically found in the plugin's PHP files under wp-content/plugins/, looking for $_GET, $_POST, or $_REQUEST parameters that are output without sanitization. Common paths include the main plugin file or any admin/frontend handler files.Affected if The plugin handles URL parameters and reflects them back into HTML output without proper escaping.
-
Review access logs for suspicious crafted URLsSearch your web server access logs (Apache error_log, Nginx access.log, or WordPress debug.log if available) for requests to your site containing the plugin's URL path with JavaScript payloads. Look for patterns like <script>, javascript:, or event handlers such as onload= or onerror= in the query string.Affected if Log entries show requests with malicious script tags or JavaScript protocols targeting your domain and containing the plugin's parameter names.
You are affected if Fugu Maintenance Switch plugin version 1.5.2 or lower is installed and active on your WordPress site, exposing reflected user input in URLs.
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.
dbcve · scopedUpdate the Fugu Maintenance Switch plugin to the latest version. If no update exists, deactivate and remove the plugin until a patched version is available.
Latest available version of Maintenance Switch plugin (version > 1.5.2)
- Check the current version of the Maintenance Switch plugin installed on the WordPress site
- Navigate to Plugins > Installed Plugins in WordPress admin dashboard
- Locate the Maintenance Switch (or Fugu Maintenance Switch) plugin
- If an update is available, click 'Update Now' to upgrade to the latest version
- Alternatively, download the latest version from the WordPress Plugin Directory and upload via Plugins > Add New > Upload Plugin
- After updating, verify the site functionality and confirm the plugin version is > 1.5.2
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Maintenance Switch
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47590 — 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-2022-47590 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