Security readout for executives and security teams
Plain-English summary
CVE-2025-54667 affects the WordPress myCred plugin through version 2.9.4.3. It is a race condition that may let an attacker affect integrity of plugin-managed operations. The cited severity is medium, with no confidentiality or availability impact stated.
Executive priority
Treat this as a moderate integrity risk for WordPress sites using myCred. Prioritize inventory and update decisions, especially where myCred controls rewards, credits, payments-adjacent workflows, or customer-facing account value.
Technical view
The issue is a CWE-367 TOCTOU race condition in myCred. CVSS 3.1 is 5.3: network reachable, low complexity, no privileges, no user interaction, unchanged scope, and low integrity impact. The source bundle does not describe exact vulnerable code paths or a confirmed fixed version.
Likely exposure
Exposure is likely limited to WordPress sites running myCred version 2.9.4.3 or earlier. Sites not using myCred are not indicated as affected by the provided sources.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The CVSS vector suggests remote triggering may be possible without authentication, but the bundle does not provide exploit details or observed abuse.
Researcher notes
The public bundle is sparse. It names CWE-367 and an affected range through <=2.9.4.3, but does not identify code paths, patch commit, fixed version, or exploitation evidence. Validate findings against official vendor guidance before drawing operational conclusions.
Mitigation direction
- Identify all WordPress sites using the myCred plugin.
- Check vendor, WordPress plugin, or Patchstack guidance for a fixed release.
- Upgrade myCred if an official fixed version is available.
- If upgrade guidance is unavailable, consider disabling myCred where business impact allows.
- Monitor point, credit, or reward activity for unusual repeated changes.
Validation and detection
- Confirm whether myCred is installed on each WordPress site.
- Record the installed myCred version and compare it to <= 2.9.4.3.
- Review plugin-managed transactions for unexpected duplicates or balance changes.
- Verify remediation against vendor or Patchstack guidance when available.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-367: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-54667 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Time-of-check Time-of-use (TOCTOU) Race Condition
Time-of-check Time-of-use (TOCTOU) Race Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.