LiveActive security incident?Get immediate response
CVE Record

CVE-2023-31216: WordPress Ultimate Member Plugin <= 2.6.0 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Ultimate Member plugin <= 2.6.0 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a medium-severity CSRF issue in the Ultimate Member WordPress plugin up to version 2.6.0. An attacker would need a logged-in user to interact with attacker-controlled content, potentially causing a low-impact unauthorized action. The provided sources do not describe data theft or service outage.

Executive priority

Treat this as a normal patch-management item, not an emergency, unless affected sites handle sensitive membership workflows or privileged account administration. Prioritize confirming plugin presence and updating affected installations through standard WordPress maintenance.

Technical view

CVE-2023-31216 is CWE-352 in Ultimate Member, package ultimate-member. CVSS 3.1 is 4.3: network reachable, low complexity, no privileges required, user interaction required, unchanged scope, low integrity impact, no confidentiality or availability impact. The bundle names versions <=2.6.0 as vulnerable.

Likely exposure

Exposure is likely limited to WordPress sites running the Ultimate Member plugin at version 2.6.0 or earlier. Sites without this plugin, or with versions not covered by the cited advisory, are not shown as affected by the provided evidence.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. Practical abuse requires social engineering or another path to make an authenticated user perform an unintended browser action.

Researcher notes

Evidence is narrow: the bundle identifies CSRF, affected plugin, CVSS, and Patchstack reference, but not a specific vulnerable endpoint, exploit details, or a named fixed version. Avoid asserting exploitation or impact beyond low integrity impact.

Mitigation direction

  • Inventory WordPress sites for the Ultimate Member plugin and installed version.
  • If running <=2.6.0, check vendor or WordPress guidance for the fixed release.
  • Upgrade or otherwise remediate according to the vendor advisory.
  • Reduce unnecessary administrative browsing while remediation is pending.
  • Monitor for unexpected Ultimate Member configuration or user-management changes.

Validation and detection

  • Confirm whether Ultimate Member is installed on each WordPress instance.
  • Record the exact plugin version and compare it with <=2.6.0 exposure.
  • Review the vendor/Patchstack advisory for current fixed-version guidance.
  • Check administrative audit logs for unexpected state changes.
  • Verify CSRF protection expectations after applying the vendor-supported update.
Prepared
Confidence
high
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-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-31216 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:N/UI:R/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:N/UI:R/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-2023-31216Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
Ultimate MemberUltimate Memberultimate-member, n/aunaffected
Weakness

CWE details

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.