Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister or obtain WordPress subscriber account
-
DeliverySend crafted HTTP request to vulnerable myCred endpoint
-
ExploitBypass missing authorization check (CWE-862)
-
ExecutionExecute privileged integrity-modifying action
-
ImpactManipulate loyalty points or reward data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to hold a valid WordPress account with at minimum subscriber-level privileges, as confirmed by the CVSS PR:L metric - unauthenticated visitors cannot exploit this flaw. The myCred plugin must be installed and active on the target WordPress installation running version 3.0.3 or earlier. On sites with open user self-registration enabled, the authentication barrier is trivially satisfied by creating a new account; on sites with closed registration, the attacker must obtain or compromise an existing subscriber account. No non-default plugin configuration or special feature enablement is identified as a prerequisite in the available data - the broken access control appears to affect the plugin in its standard active state. The primary limiting factors are the authentication requirement (PR:L) and the plugin's presence, meaning the realistic risk surface is open-registration WordPress sites using myCred for loyalty or reward functionality. |
| Impact | The CVSS 6.5 Medium score is driven by network accessibility, low attack complexity, and high integrity impact, tempered by the PR:L requirement (subscriber authentication). No EPSS score was included in the provided intelligence package, so probabilistic exploitation likelihood cannot be quantified from this data. The vulnerability is not listed in the CISA KEV catalog, and no POC code has been confirmed. In practical terms, the PR:L prerequisite is the primary mitigating factor: an attacker must first hold a valid subscriber-level WordPress account. On sites with open user registration, this barrier is trivial - any visitor can self-register and immediately attempt exploitation; on closed-registration sites, the attacker must compromise or socially engineer an existing account. The I:H integrity rating signals that successful exploitation could allow unauthorized manipulation of points balances or reward records, which carries real business impact for organizations running loyalty programs on myCred. CVSS accurately reflects the threat model here - this is a genuine medium-severity issue on registration-open sites and a reduced-priority finding on tightly controlled installations. |
| Exploit ScenarioDerived | An attacker registers a free account on a WordPress site with open user registration, gaining subscriber-level access, then crafts an HTTP request targeting a myCred plugin endpoint that performs a privileged operation such as adjusting a user's point balance. Because the endpoint lacks authorization checks (CWE-862), the plugin processes the request as if the subscriber were a privileged administrator, allowing the attacker to credit themselves with arbitrary loyalty points or trigger unauthorized reward redemptions. No public exploit code has been identified at time of analysis, but the AC:L and UI:N CVSS metrics indicate the attack requires no special conditions or timing beyond holding a valid subscriber account. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 15, 2026
Broken access control in the myCred WordPress plugin (all versions through 3.0.3) allows authenticated users with only subscriber-level privileges to bypass authorization checks and perform actions reserved for higher-privileged roles, yielding high integrity impact on affected installations. The root cause is missing authorization enforcement (CWE-862) on one or more plugin endpoints, meaning the plugin executes sensitive operations - such as manipulating loyalty points or reward data - without verifying the requesting user's actual capabilities. No public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog, but the low complexity and no-user-interaction requirement make exploitation straightforward for any attacker holding a valid account.
RemediationAI
No patched version is explicitly identified in the available intelligence data; the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/mycred/vulnerability/wordpress-mycred-plugin-3-0-3-broken-access-control-vulnerability should be checked for the confirmed fix version and upgrade instructions. As an immediate compensating control, administrators should disable open user registration (WordPress Admin > Settings > General > uncheck 'Anyone can register') to eliminate the self-registration path that lowers the attack barrier to zero - this has no impact on existing accounts but prevents new attacker-controlled subscriber accounts from being created. Where disabling registration is not feasible, consider applying a web application firewall rule to restrict POST requests to myCred plugin endpoints from subscriber-role sessions, accepting the trade-off that legitimate subscriber-facing myCred features may be disrupted. Sites should also audit recent myCred point transaction logs for anomalous self-crediting or unexpected reward redemptions as indicators of prior exploitation.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
myCred is a WordPress plugin that implements gamification systems including loyalty points, badges, and reward management for WordPress sites. CWE-862 (Missing Authorization) describes a failure to enforce access control checks before executing a privileged action - in WordPress terms, this means the plugin does not verify the current user's capabilities (e.g., via current_user_can()) before processing a sensitive request. The CVSS vector confirms network delivery (AV:N) with low attack complexity (AC:L), subscriber-level authentication (PR:L), and no user interaction (UI:N). The scope is unchanged (S:U), indicating the impact is contained to the myCred plugin's own data plane rather than escaping to the broader WordPress installation. The affected CPE is cpe:2.3:a:mycred:mycred:*:*:*:*:*:*:*:*, covering all versions through 3.0.3 as reported by Patchstack and corroborated by ENISA EUVD-2026-36997.
Know when Mycred gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Network-accessible WordPress plugin endpoint requires only subscriber authentication (PR:L); integrity-only impact because attackers alter points/reward data but gain no confidentiality or availability leverage.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Subscriber Broken Access Control in myCred <= 3.0.3 versions.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
The myCred WordPress plugin before 2.3 does not validate or escape the fields parameter before using it in a SQL stateme
Payment gateway merchant account verification is entirely absent in the myCred WordPress plugin before version 3.2.5, en
The myCred WordPress plugin before 2.4.3.1 does not have authorisation and CSRF checks in its mycred-tools-import-export
The myCred WordPress plugin before 2.4.3.1 does not have any authorisation and CSRF checks in the mycred-tools-import-ex
The myCred WordPress plugin before 2.4.4.1 does not have any authorisation in place in its mycred-tools-select-user AJAX
Broken access control in the Bookify WordPress plugin (versions ≤ 1.1.1) allows authenticated subscriber-level users to
Unauthenticated IDOR in License Manager for WooCommerce (versions <= 3.0.15) allows remote, unauthenticated attackers to
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Saad Iqbal myCred
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in myCred myCred - Po
Cross-Site Request Forgery (CSRF) vulnerability in myCred plugin <= 2.5 versions. Rated medium severity (CVSS 6.5), this
Stored XSS in the myCred WordPress plugin (versions through 3.0.4) enables authenticated low-privileged attackers to per
Missing Authorization in the myCred WordPress plugin (all versions through 3.1.2) allows authenticated low-privileged us
EUVD-2026-36997
GHSA-98j9-frcv-j6pw
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB