CVE-2025-49872
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 · uneditedMissing Authorization vulnerability in Saad Iqbal myCred mycred allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects myCred: from n/a through <= 2.9.4.2.
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 confidenceMissing Authorization (Broken Access Control) vulnerability in myCred plugin allows users to access functionality not properly constrained by Access Control Lists (ACLs). This means an authenticated user can potentially perform actions or access features that should be restricted based on their user role or permissions.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm myCred plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'myCred' plugin. Alternatively, check the /wp-content/plugins/ directory for the myCred folder.Affected if myCred plugin is installed and active
-
Identify installed myCred versionIn WordPress admin, go to Plugins > Installed Plugins, find myCred, and note the version number displayed. Alternatively, check the mycred.php file header for 'Version:' tag.Affected if version cannot be determined or is unknown
-
Check for exposed admin AJAX endpointsInspect the wp-admin/admin-ajax.php responses when calling myCred action hooks (such as mycred_delete_logs, mycred_reset_balance, or similar). Use a low-privilege user account (subscriber level) to test if these endpoints return expected access denied errors.Affected if AJAX actions related to myCred return success or data instead of a permission denied error for low-privilege users
-
Verify role-based access control on myCred functionsCreate or use a test user with a low role (e.g., Subscriber). Attempt to access myCred admin pages directly via URL or trigger management actions (such as modifying point balances, managing badges, or changing settings) that should require administrator privileges.Affected if low-privilege users can access or modify myCred settings, point balances, or administrative functions
-
Review user capability checks in myCred codeIf code access is available, search the myCred plugin files for 'current_user_can' or 'capability' checks around sensitive functions. Look for missing or insufficient checks before executing privileged operations.Affected if critical functions lack proper current_user_can() validation
A user is affected if the myCred plugin is installed and low-privilege authenticated users can access administrative functions, modify point balances, or perform actions that should require higher permissions.
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 proper capability checks and role-based access controls on all sensitive functions within the myCred plugin, ensuring that each action verifies the current user has the appropriate permissions before execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49872 — 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-49872 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