LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24951: WordPress myCred plugin <= 2.9.7.3 - Broken Access Control vulnerability

Missing Authorization vulnerability in Saad Iqbal myCred mycred allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects myCred: from n/a through <= 2.9.7.3.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24951 is a broken access control issue in the WordPress myCred plugin through version 2.9.7.3. A logged-in user may be able to perform an action they should not be allowed to perform. The documented impact is limited integrity impact, not data theft or service outage.

Executive priority

Treat as a near-term maintenance priority, not an emergency based on current evidence. Prioritize public WordPress sites with user accounts, loyalty points, rewards, or credit-like workflows because unauthorized integrity changes may create business or fraud exposure.

Technical view

The CVE describes missing authorization in Saad Iqbal myCred for WordPress, classified as CWE-862. CVSS 3.1 is 4.3: network exploitable, low complexity, low privileges required, no user interaction, unchanged scope, integrity low only. Public details do not specify the exact vulnerable endpoint or action.

Likely exposure

Exposure is likely limited to WordPress sites running the myCred plugin at version 2.9.7.3 or earlier, where untrusted or lower-privileged users can log in. Sites without the plugin, or without user registration/login exposure, are less likely to be affected.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not marked KEV. Exploitation requires an authenticated user with low privileges. The business risk is unauthorized modification or abuse of plugin-controlled functionality, depending on how myCred is configured.

Researcher notes

Evidence is sparse. The CVE and Patchstack entry identify broken access control but do not provide endpoint-level detail or a named fixed version in the supplied bundle. The record’s affected metadata is less clear than the description, so validate against vendor and Patchstack advisories.

Mitigation direction

  • Inventory WordPress sites for the myCred plugin and record installed versions.
  • Prioritize sites running myCred version 2.9.7.3 or earlier.
  • Check myCred, WordPress.org, or Patchstack guidance for a fixed version or vendor workaround.
  • Update the plugin if a vendor-supported fixed release is available.
  • Limit account creation and low-privilege access on affected sites where possible.
  • Review myCred roles and permissions for unnecessary delegated capabilities.

Validation and detection

  • Confirm whether myCred is installed on each WordPress site.
  • Verify the installed plugin version against the affected range through 2.9.7.3.
  • Review application logs for unauthorized myCred point, balance, or configuration changes.
  • Test authorization boundaries only in an approved staging environment.
  • Confirm remediation by rechecking plugin version and role permissions after changes.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookup
cve · low confidence lookup

CVE-2026-24951 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-24951Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Saad IqbalmyCredmycred, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.