CVE-2026-24951
Missing Authorization in myCred Plugin Allows Privilege Escalation
Publication date: 2026-02-03
Last updated on: 2026-02-03
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| mycred | mycred | to 2.9.7.3 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
CVE-2026-24951 is a Broken Access Control vulnerability that allows unprivileged users to perform actions reserved for higher-privileged roles due to missing authorization checks.
While the vulnerability involves access control issues, the provided information does not specify any direct impact on compliance with common standards and regulations such as GDPR or HIPAA.
However, broken access control vulnerabilities can potentially lead to unauthorized access to sensitive data, which might indirectly affect compliance with data protection regulations if exploited.
Users are advised to update to version 2.9.7.4 or later to mitigate the risk.
Can you explain this vulnerability to me?
CVE-2026-24951 is a Broken Access Control vulnerability found in the WordPress myCred plugin versions up to and including 2.9.7.3.
The issue arises from missing authorization, authentication, or nonce token checks within certain functions, which allows unprivileged users (even those with only subscriber-level privileges) to perform actions that should be restricted to higher-privileged roles.
This vulnerability is classified under the OWASP Top 10 category A1: Broken Access Control and has a low severity rating with a CVSS score of 4.3.
How can this vulnerability impact me? :
This vulnerability allows users with low-level privileges to perform actions reserved for higher-privileged roles, potentially leading to unauthorized changes or access within the myCred plugin.
Although the severity is considered low and the threat impact is not significant, it still poses a risk of unauthorized access or modification within the affected system.
Users are advised to update to version 2.9.7.4 or later of the myCred plugin to mitigate this risk.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability is related to missing authorization checks in the WordPress myCred plugin versions up to 2.9.7.3, allowing subscriber-level users to perform unauthorized actions.'}, {'type': 'paragraph', 'content': 'Detection typically involves verifying the plugin version installed on your WordPress site and checking for unauthorized privilege escalations or actions performed by subscriber-level accounts.'}, {'type': 'paragraph', 'content': 'You can detect the vulnerable plugin version by running the following command on your WordPress installation directory:'}, {'type': 'list_item', 'content': "grep -i 'Version' wp-content/plugins/mycred/mycred.php"}, {'type': 'paragraph', 'content': 'Alternatively, you can check the plugin version from the WordPress admin dashboard under Plugins.'}, {'type': 'paragraph', 'content': 'To detect exploitation attempts, review your WordPress logs for actions performed by subscriber-level users that should require higher privileges.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the myCred plugin to version 2.9.7.4 or later, where the vulnerability has been fixed.
If updating immediately is not possible, restrict subscriber-level user permissions temporarily to prevent unauthorized actions.
Consider using automated update tools such as Patchstack to rapidly apply security patches to vulnerable plugins.
Regularly monitor your WordPress site for suspicious activity and review access control settings.