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

CVE-2026-57655

HIGH · 8.2 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable No privileges 8 weeks old

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
Unauthenticated Cross Site Request Forgery (CSRF) in Child Theme Wizard <= 1.4 versions.

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 confidence

Unauthenticated Cross Site Request Forgery (CSRF) vulnerability in Child Theme Wizard plugin versions 1.4 and below allows remote attackers to craft malicious requests that trick authenticated administrators into performing unintended actions such as theme installations or modifications.

MitigationUpdate Child Theme Wizard to the latest patched version. If no patch is available, disable or remove the plugin. Implement anti-CSRF tokens on all state-changing actions.

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
Changed
Confidentiality
None
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:L

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 Child Theme Wizard plugin is installed
    Check if the /wp-content/plugins/child-theme-wizard/ directory exists on the WordPress server file system
    Affected if The plugin directory does not exist, meaning the plugin is not installed and the site is not affected
  2. Determine the installed plugin version
    Open the main plugin file (child-theme-wizard.php) and locate the 'Version:' header in the plugin comments, or check readme.txt for the version field
    Affected if The reported version is 1.4 or lower, indicating the vulnerable version is present
  3. Confirm the plugin is active
    Log into WordPress admin panel and navigate to Plugins > Installed Plugins, or query the wp_options table for option_name='active_plugins' to check if Child Theme Wizard is enabled
    Affected if The plugin is active and running, making the CSRF vulnerability exploitable against authenticated administrators
  4. Check admin access to plugin functionality
    Navigate to the WordPress admin menu to locate the Child Theme Wizard menu item (typically under Appearance or Tools), or check if the plugin registers any admin menu pages
    Affected if The plugin menu is accessible in the admin dashboard, meaning administrators can be targeted for CSRF attacks

A site is affected if Child Theme Wizard plugin version 1.4 or lower is installed, active, and accessible in the WordPress admin panel, allowing unauthenticated attackers to craft malicious CSRF requests targeting authenticated administrators.

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

Update Child Theme Wizard to the latest patched version. If no patch is available, disable or remove the plugin. Implement anti-CSRF tokens on all state-changing actions.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57655 — 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-57655 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