CVE-2025-14064
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 · uneditedThe BuddyTask plugin for WordPress is vulnerable to unauthorized access and modification of data due to a missing capability check on multiple AJAX endpoints in all versions up to, and including, 1.3.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to view, create, modify, and delete task boards belonging to any BuddyPress group, including private and hidden groups they are not members of.
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 confidenceThe BuddyTask WordPress plugin versions up to 1.3.0 contain multiple AJAX endpoints that lack proper capability verification. Any authenticated user with Subscriber-level access or higher can invoke these endpoints to view, create, modify, or delete task boards belonging to any BuddyPress group—including private and hidden groups the attacker is not a member of—due to missing authorization checks.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm BuddyTask plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'BuddyTask' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'buddytask'.Affected if The BuddyTask plugin is present in the WordPress installation.
-
Identify installed plugin versionIn the WordPress admin, go to Plugins > Installed Plugins. Find BuddyTask and locate the version number displayed below the plugin name. If using FTP or file manager, open /wp-content/plugins/buddytask/readme.txt and look for the version number in the header section.Affected if The installed version is 1.3.0 or lower.
-
Verify AJAX functionality is accessibleCheck if the WordPress site has AJAX endpoints active. For BuddyTask, the vulnerable endpoints typically respond to wp-admin/admin-ajax.php?action=buddytask_*. Test by sending an authenticated request (any Subscriber-level user account will suffice) to one of these endpoints.Affected if AJAX endpoints respond to authenticated requests without proper capability checks.
-
Confirm user role configurationIn WordPress admin, go to Users > Users List. Verify that there exist users with the Subscriber role or higher (Contributor, Author, Editor, Administrator). The vulnerability affects any authenticated user at Subscriber level or above.Affected if There is at least one user with Subscriber-level access or higher, and the plugin version is 1.3.0 or lower.
A user is affected if the BuddyTask plugin is installed, active, and running version 1.3.0 or lower, with at least one authenticated user role present in the WordPress site.
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 dataUpdate to version 1.3.1 or later which implements proper capability checks on AJAX endpoints; alternatively, disable the plugin until the patch can be applied.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14064 — 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-2025-14064 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