CVE-2026-27368
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 SeedProd Coming Soon Page, Under Construction & Maintenance Mode by SeedProd coming-soon allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Coming Soon Page, Under Construction & Maintenance Mode by SeedProd: from n/a through <= 6.19.8.
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 confidenceMissing Authorization vulnerability in SeedProd Coming Soon Page plugin allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly enforce authorization checks on certain functionalities, potentially allowing unauthenticated users to access or modify maintenance mode settings.
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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Confirm SeedProd plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'SeedProd Coming Soon Page' or 'SeedProd' in the plugin list.Affected if The plugin appears in the installed plugins list and is activated
-
Identify installed plugin versionIn the plugin list, click on the plugin name or view the plugin files. The version number is typically displayed in the plugin header or on the plugin's main settings page.Affected if The version cannot be determined or is older than the fixed version released for this CVE
-
Test maintenance mode endpoint accessibilityUse a tool like curl or Burp Suite to send a request to common SeedProd API endpoints (typically /wp-json/seedprod/v1/settings or similar /wp-json/seedprod/* endpoints) WITHOUT providing authentication credentials.Affected if The endpoint returns a successful response with maintenance mode settings or allows modification without requiring authentication (returns 200 OK instead of 401 Unauthorized or 403 Forbidden)
-
Inspect plugin capability checksReview the plugin's PHP source code, specifically looking for function calls like current_user_can(), wp_verify_nonce(), or REST API permission_callback definitions in the plugin's rest-api folder.Affected if The code shows missing or inadequate capability checks on endpoints that modify maintenance mode settings
A user is affected if the SeedProd Coming Soon Page plugin is installed and its maintenance mode or settings endpoints can be accessed or modified by unauthenticated users without proper authorization validation.
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 SeedProd Coming Soon Page plugin to the latest version immediately. Review and enforce proper authorization checks on all sensitive endpoints and functionalities within the plugin.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27368 — 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-2026-27368 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