Template DebuggerWordPress extension · Template Debugger Project
CVE-2023-35773
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 Danny Hearnah - ChubbyNinjaa Template Debugger plugin <= 3.1.2 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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the ChubbyNinjaa Template Debugger WordPress plugin versions 3.1.2 and below. The plugin lacks proper anti-CSRF token validation on state-changing operations, allowing unauthenticated attackers to trick authenticated administrators into performing unintended actions such as modifying plugin settings or executing administrative functions.
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
Template DebuggerWordPress extension
<= 3.1.2CVSS 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.
-
Locate the Template Debugger plugin filesNavigate to your WordPress installation /wp-content/plugins/ directory and locate the 'template-debugger' folder or a folder containing 'Template Debugger' in the name.Affected if The plugin folder exists and contains plugin files.
-
Determine the installed plugin versionOpen the main plugin PHP file (often named similarly to the plugin folder) and locate the 'Version:' header in the plugin comment block at the top of the file. Alternatively, check the 'Stable tag' in readme.txt if present.Affected if The reported version is 3.1.2 or lower (any version <= 3.1.2).
-
Verify the plugin is active on the WordPress siteLog into the WordPress admin dashboard, go to Plugins > Installed Plugins, and check if 'Template Debugger' or 'ChubbyNinjaa Template Debugger' shows as 'Active'.Affected if The plugin is currently active.
-
Inspect plugin for CSRF protection mechanismsReview the main plugin PHP files for the presence of 'wp_verify_nonce', 'check_admin_referer', 'check_ajax_referer', or similar nonce verification functions. Search for these functions in any file handling form submissions or AJAX actions.Affected if No nonce verification functions are found in files that handle state-changing operations (settings changes, administrative actions).
A user is affected if the Template Debugger plugin is installed, active, and running version 3.1.2 or lower without proper nonce validation on its state-changing operations.
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) on all forms and AJAX actions, and validate the request origin via nonce verification or Referer header checks. Update to the latest plugin version when a patched release becomes available.
Fix this in Template Debugger
Scoped from the published advisory
- Consultation1.0 h
- Implementation3.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 $1,952.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35773 — 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-2023-35773 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