CVE-2022-47429
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 · uneditedMissing Authorization vulnerability in 8Degree Themes Coming Soon Landing Page and Maintenance Mode WordPress Plugin allows Retrieve Embedded Sensitive Data.This issue affects Coming Soon Landing Page and Maintenance Mode WordPress Plugin: from n/a through 2.2.0.
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 confidenceThe 8Degree Themes Coming Soon Landing Page and Maintenance Mode WordPress plugin versions 2.2.0 and below contain a missing authorization vulnerability that allows unauthenticated or unauthorized users to retrieve embedded sensitive data. This is an access control failure where the plugin fails to properly validate user permissions before exposing sensitive information through the coming soon or maintenance mode functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 plugin installationCheck your WordPress plugins directory (wp-content/plugins/) for a folder named 'coming-soon-landing-page-maintenance-mode' or similar 8degree themes plugin directory. If using WordPress admin, list installed plugins and look for 'Coming Soon Landing Page & Maintenance Mode' by 8Degree Themes.Affected if The plugin folder exists in wp-content/plugins/
-
Determine installed plugin versionOpen the main plugin PHP file (usually the first PHP file in the plugin folder) and check the plugin header comment for the 'Version' field. Alternatively, in WordPress admin, go to Plugins > Installed Plugins and find the version listed for this plugin.Affected if The reported version is 2.2.0 or lower
-
Verify if coming soon or maintenance mode is activeCheck the plugin settings through WordPress admin (Settings > Coming Soon or the plugin's settings page) to see if the coming soon or maintenance mode feature is currently enabled and serving a landing page to visitors.Affected if The coming soon or maintenance mode is enabled and publicly accessible
-
Confirm unauthenticated access is possibleOpen your website in a private/incognito browser window (without being logged into WordPress) to see if you can view the coming soon page or any sensitive data that should require authorization.Affected if Unauthenticated visitors can access the coming soon page or view sensitive embedded data without logging in
You are affected if the 8Degree Themes Coming Soon Landing Page & Maintenance Mode plugin version 2.2.0 or lower is installed with the coming soon/maintenance mode feature enabled and accessible to unauthenticated visitors.
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 the Coming Soon Landing Page and Maintenance Mode plugin to version 2.2.1 or later, which contains proper authorization checks. Until updated, restrict access to the wp-admin area and monitor for unauthorized access attempts.
- Consultation2.0 h
- Implementation4.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47429 — 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-47429 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