dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-34896

HIGH · 7.5 CVSS v3.1 Published 2026-04-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in Analytify Under Construction, Coming Soon & Maintenance Mode allows Cross Site Request Forgery.This issue affects Under Construction, Coming Soon & Maintenance Mode: from n/a through 2.1.1.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the 'Analytify Under Construction, Coming Soon & Maintenance Mode' WordPress plugin. Attackers can trick authenticated administrators into unknowingly submitting malicious requests to the plugin's administrative functions, potentially modifying site settings or performing unauthorized actions.

MitigationImplement anti-CSRF nonce tokens (wp_verify_nonce) on all state-changing operations (forms, AJAX endpoints, admin actions) within the plugin, and validate the nonce on the server side before processing any requests.

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify the plugin is installed
    Navigate to WordPress Admin > Plugins and locate 'Analytify Under Construction, Coming Soon & Maintenance Mode' in the installed plugins list
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed plugin version
    Click on the plugin name/details in the Plugins admin page to view the version number, or inspect the plugin header in wp-content/plugins/analytify-coming-soon/main.php for the 'Version' comment
    Affected if A version number is displayed (compare to any publicly available affected version information)
  3. Locate plugin administrative forms
    Search the plugin directory for PHP files containing form tags (grep -r '<form' /wp-content/plugins/analytify-coming-soon/) and identify forms that perform state-changing operations (settings saves, option updates)
    Affected if Administrative forms exist that accept user input for plugin settings
  4. Inspect forms for CSRF nonce tokens
    Examine each identified form HTML to check for a hidden nonce field (typically wp_nonce_field or similar), and verify the nonce is submitted with the form
    Affected if Forms lack a hidden nonce field or token input
  5. Check AJAX endpoints for nonce verification
    Search for wp_ajax_ and wp_ajax_nopriv_ hooks in plugin PHP files (grep -r 'wp_ajax_' /wp-content/plugins/analytify-coming-soon/), then verify each handler calls wp_verify_nonce or check_admin_referer before processing
    Affected if AJAX handlers process requests without verifying a nonce
  6. Review admin action handlers for nonce validation
    Search for add_action calls handling admin POST/GET requests (settings updates, option changes), then verify each calls wp_verify_nonce or check_admin_referer before executing state-changing logic
    Affected if Admin action handlers process requests without nonce verification

You are affected if the plugin is installed AND any of its administrative forms, AJAX endpoints, or action handlers lack CSRF nonce validation before processing requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF nonce tokens (wp_verify_nonce) on all state-changing operations (forms, AJAX endpoints, admin actions) within the plugin, and validate the nonce on the server side before processing any requests.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34896 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34896 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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