LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27440: WordPress myCred plugin <= 2.9.7.6 - Cross Site Scripting (XSS) vulnerability

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Saad Iqbal myCred mycred allows Stored XSS.This issue affects myCred: from n/a through <= 2.9.7.6.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-27440 is a stored cross-site scripting issue in the WordPress myCred plugin through version 2.9.7.6. An authenticated attacker may be able to save malicious script content that later runs in another user’s browser. Business risk is moderate, especially for sites with many contributors or customer-facing account features.

Executive priority

Treat as a medium-priority web application risk. It is not currently evidenced as actively exploited in the provided sources, but stored XSS can support account compromise, admin-session abuse, or site defacement if triggered in privileged user browsers.

Technical view

The CVE describes CWE-79 improper neutralization during web page generation in Saad Iqbal myCred. CVSS 3.1 is 6.5: network-accessible, low complexity, low privileges required, user interaction required, scope changed, with low confidentiality, integrity, and availability impact. The vulnerable range is reported as myCred through <= 2.9.7.6.

Likely exposure

Exposure is likely limited to WordPress sites running the myCred plugin at version 2.9.7.6 or earlier, particularly where untrusted or lower-privileged users can submit content processed by the plugin.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. The CVSS vector indicates exploitation requires low privileges and user interaction, consistent with stored XSS that triggers when another user views affected content.

Researcher notes

Evidence is limited to the CVE record and Patchstack database entry. The affected range is stated as <= 2.9.7.6, but the source bundle does not name a specific fixed version or vulnerable parameter. Avoid assuming affected workflows without vendor detail or testing authorization.

Mitigation direction

  • Inventory WordPress sites for the myCred plugin and version.
  • Prioritize sites running myCred 2.9.7.6 or earlier.
  • Check vendor and Patchstack guidance for a fixed release.
  • Upgrade beyond the affected range when a trusted fixed version is available.
  • Restrict untrusted user access to myCred-related submission workflows until remediated.

Validation and detection

  • Confirm installed myCred versions across WordPress assets.
  • Review whether any site allows low-privileged users to submit myCred-handled content.
  • Check security plugins or logs for suspicious stored script indicators.
  • Verify remediation by confirming the plugin is no longer within the affected range.
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-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-27440 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
6.5 (3.1)
Known Exploited
No
Published

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

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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L2.33.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.