Security readout for executives and security teams
Plain-English summary
CVE-2023-24417 is a medium-severity CSRF issue in the WordPress Worthy VG WORT integration plugin through version 1.6.5-6497609. A victim would need to interact while authenticated, and the reported impact is limited integrity change. No provided source confirms active exploitation.
Executive priority
Treat this as a normal-priority WordPress hygiene issue unless the plugin is deployed on important public sites. The impact is not described as data theft or outage, but unauthorized configuration or content changes may still create business risk.
Technical view
The issue is CWE-352 Cross-Site Request Forgery affecting tiggersWelt.net Worthy for WordPress. CVSS 3.1 is 4.3 with network attack vector, low complexity, no attacker privileges, required user interaction, unchanged scope, and low integrity impact only. The source bundle does not identify the vulnerable action or endpoint.
Likely exposure
Exposure is limited to WordPress sites running the Worthy wp-worthy plugin at or below 1.6.5-6497609. Sites not using this plugin are not indicated as affected by the supplied sources.
Exploitation context
The CVE is not listed as KEV, and the supplied sources do not report exploitation in the wild. Practical exploitation would depend on tricking an authenticated WordPress user into a forged action; exact privileges and action are not documented here.
Researcher notes
Evidence is sparse. The sources provide CWE, CVSS, product, and affected version threshold, but not vulnerable parameters, endpoints, fixed version, or exploit telemetry. Avoid asserting broader WordPress exposure beyond the Worthy plugin.
Mitigation direction
- Inventory WordPress sites for the Worthy wp-worthy plugin and record installed versions.
- Check vendor or Patchstack guidance for a fixed version or official workaround.
- Update the plugin if a maintained fixed release is available.
- Disable or remove the plugin where it is unnecessary or cannot be verified safe.
- Prioritize higher-value sites and accounts with administrative WordPress access.
Validation and detection
- Confirm whether wp-worthy is installed on each WordPress site.
- Compare installed plugin versions against the affected threshold, <= 1.6.5-6497609.
- Review CVE and Patchstack entries for any newly published remediation details.
- Check WordPress audit logs for unexpected Worthy configuration or content changes.
- Document compensating action if no vendor fix is 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-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 lookupCVE-2023-24417 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
- 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
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:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
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.