LiveActive security incident?Get immediate response
CVE Record

CVE-2023-35096: WordPress myCred Plugin <= 2.5 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in myCred plugin <= 2.5 versions.

MediumCVSS 5.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-35096 is a medium-severity CSRF issue in the WordPress myCred plugin up to version 2.5. It may let an attacker cause unintended actions through a vulnerable site workflow. The public bundle does not identify the exact action, affected role, patch version, or active exploitation.

Executive priority

Prioritize this as a routine but time-bound WordPress plugin remediation. It is not currently evidenced as exploited, but affected public sites should be inventoried and updated through official guidance.

Technical view

The issue is classified as CWE-352, Cross-Site Request Forgery, in myCred for WordPress <= 2.5. The CVSS 3.1 score is 5.4 with low integrity and availability impact and no confidentiality impact. Available sources do not describe the vulnerable endpoint, nonce failure, authorization context, or remediation version.

Likely exposure

Exposure is most likely on WordPress sites with the myCred plugin installed at version 2.5 or earlier. Sites not using myCred are not indicated as affected by the supplied sources.

Exploitation context

The CVE is not in CISA KEV, and the provided sources do not report active exploitation. Because the issue is CSRF, real-world risk depends on what site action can be triggered, which is not described in the bundle.

Researcher notes

The public bundle is thin. It confirms CSRF classification, affected plugin family, <=2.5 title scope, CVSS, and Patchstack reference, but lacks endpoint, privilege context, exploitability details, and fixed-version data.

Mitigation direction

  • Inventory WordPress sites for myCred and record installed versions.
  • Treat myCred version 2.5 or earlier as potentially affected.
  • Check myCred and Patchstack guidance for the fixed release or official mitigation.
  • Apply the vendor-supported update when identified and tested.
  • Consider disabling myCred where risk outweighs business need until remediated.

Validation and detection

  • Confirm whether myCred is installed on each WordPress site.
  • Verify the installed myCred version against the <= 2.5 affected range.
  • Review vendor or Patchstack advisories for fixed-version details.
  • Check web server and WordPress logs for unusual myCred-related state changes.
  • Document whether compensating controls or plugin removal were applied.
Prepared
Confidence
medium
Sources
3

Public sources used

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-352: 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-2023-35096 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
5.4 (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: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
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L3.92.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-35096Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
myCredmyCredmycred, n/aunaffected
Weakness

CWE details

CWE-352

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs