CVE-2026-24574
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 Recorp Export WP Page to Static HTML/CSS allows Cross Site Request Forgery. This issue affects Export WP Page to Static HTML/CSS: from n/a through 6.0.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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Export WP Page to Static HTML/CSS WordPress plugin (versions up to 6.0.0) allows attackers to trick authenticated administrators into performing unintended actions by leveraging the lack of anti-CSRF token validation on state-changing 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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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.
-
Verify the plugin is installedNavigate to WordPress admin dashboard > Plugins and confirm 'Export WP Page to Static HTML/CSS' plugin is activeAffected if The plugin is installed and active
-
Check the installed plugin versionIn Plugins list, click on the plugin name to view version details, then compare against the affected version range if knownAffected if The installed version falls within the vulnerable version range (if version data becomes available)
-
Locate the plugin export functionality filesAccess the WordPress plugin directory via FTP or file manager, navigate to /wp-content/plugins/export-wp-page-to-static-html-css/ and identify the main export PHP filesAffected if Export-related PHP files exist in the plugin directory
-
Inspect export code for nonce validationOpen the main export PHP file(s) and search for 'nonce' or 'wp_verify_nonce' function calls within the export handler functionsAffected if No nonce verification is found in the export action handler, or nonce verification is missing entirely
-
Check form and AJAX calls for CSRF tokensReview any HTML forms or JavaScript AJAX calls that trigger the export function to verify if _wpnonce or similar CSRF token fields are includedAffected if Export forms or AJAX requests do not include CSRF token parameters
A user is affected if the Export WP Page to Static HTML/CSS plugin is installed and the export functionality lacks proper nonce/CSRF token validation in its 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 anti-CSRF tokens (nonces) for all administrative actions and add proper origin/referer header validation to prevent cross-site request forgery attacks.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24574 — 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-24574 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