Maintenance NoticeWordPress extension · Codevibrant
CVE-2025-28859
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in CodeVibrant Maintenance Notice maintenance-notice allows Cross Site Request Forgery.This issue affects Maintenance Notice: from n/a through <= 1.0.6.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the CodeVibrant Maintenance Notice WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions, such as modifying maintenance mode settings, through maliciously crafted requests.
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 NoticeWordPress extension
<= 1.0.5CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 plugin is installedCheck your WordPress installation's wp-content/plugins directory for the 'maintenance-notice' or 'cv-maintenance-notice' folder, or view the installed plugins list via WordPress admin under Plugins > Installed PluginsAffected if The CodeVibrant Maintenance Notice plugin appears in your installed plugins list
-
Determine installed versionOpen the main plugin PHP file (typically maintenance-notice.php or cv-maintenance-notice.php) and locate the 'Version' header in the plugin comment block, or check the plugin row in WordPress admin plugins listAffected if The version number is 1.0.5 or lower (the vulnerable range is <= 1.0.5)
-
Inspect form handlers for nonce verificationExamine the main plugin PHP file and any included files for form processing functions; search for occurrences of 'wp_nonce_field', 'wp_nonce', 'check_admin_referer', or 'check_ajax_referer'Affected if No nonce-related function calls are found in the plugin's form handling code, indicating CSRF protection is missing
-
Inspect AJAX handlers for nonce verificationLocate any add_action('wp_ajax_') and add_action('wp_ajax_nopriv_') hooks in the plugin; examine the callback functions for nonce validation callsAffected if AJAX handlers lack nonce verification (no check_admin_referer or check_ajax_referer calls before processing requests)
You are affected if the CodeVibrant Maintenance Notice plugin version is 1.0.5 or lower AND the plugin code contains no nonce verification in its form submissions and AJAX request handlers.
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 dataImplement WordPress nonces (anti-CSRF tokens) on all form submissions and AJAX requests within the plugin, and verify the nonce before processing any state-changing operations.
Fix this in Maintenance Notice
Scoped from the published advisory
- 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-2025-28859 — 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-2025-28859 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