dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-64636

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 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 Broken Access Control in Donation Thermometer <= 2.2.7 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 confidence

The Donation Thermometer WordPress plugin versions 2.2.7 and below contains an unauthenticated broken access control vulnerability, allowing unauthenticated attackers to access functionality that should require proper authorization.

MitigationUpdate the Donation Thermometer plugin to a version newer than 2.2.7. If no patched version is available, disable the plugin or implement web application firewall rules to restrict unauthorized access.

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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checks

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

  1. Locate the Donation Thermometer plugin installation
    Check your WordPress plugins directory at wp-content/plugins/ for a folder named 'donation-thermometer' or similar variant. If using WP-CLI, run: wp plugin list --status=active --format=csv
    Affected if The plugin folder exists in the plugins directory and the plugin is active
  2. Determine the installed plugin version
    Open the main plugin file (often donation-thermometer.php) or readme.txt in the plugin folder and locate the 'Version:' field in the plugin header comments. Alternatively, access WordPress Admin > Plugins and read the version displayed there.
    Affected if The version displayed is 2.2.7 or lower (e.g., 2.2.7, 2.2.6, 2.2.5, etc.)
  3. Verify the plugin is processing requests without authentication
    Examine the plugin PHP code for AJAX handlers or action callbacks that lack current_user_can() or wp_verify_nonce() checks, particularly those registered with add_action('wp_ajax_...') or add_action('wp_ajax_nopriv_...'). Look for functions that should require admin privileges but are accessible to unauthenticated users.
    Affected if The plugin contains functionality accessible to unauthenticated users (wp_ajax_nopriv hooks) that should be restricted to authenticated administrators only

Your environment is affected if the Donation Thermometer plugin is installed with version 2.2.7 or lower and exposes admin-only functionality to unauthenticated users.

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 the Donation Thermometer plugin to a version newer than 2.2.7. If no patched version is available, disable the plugin or implement web application firewall rules to restrict unauthorized access.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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