Security readout for executives and security teams
Plain-English summary
CVE-2024-51679 affects the WordPress Appointmind plugin through version 4.0.0. A malicious site or request could abuse a user’s browser interaction to store script in the site, creating stored cross-site scripting risk. The record rates it high severity, but the provided sources do not show confirmed active exploitation.
Executive priority
Treat this as a high-priority WordPress plugin exposure, especially on externally facing sites. It is not documented as actively exploited in the provided sources, but stored XSS can create durable compromise paths and reputational risk if attackers reach users through trusted site pages.
Technical view
The issue is a CSRF vulnerability in gentlesource Appointmind that can lead to stored XSS. The CVSS 3.1 score is 7.1 with network attack vector, low complexity, no attacker privileges, required user interaction, and changed scope. Affected scope is stated as Appointmind through <= 4.0.0.
Likely exposure
Exposure is limited to WordPress installations running the Appointmind plugin at version 4.0.0 or earlier. The provided CPE and version metadata is sparse, so asset confirmation should rely on WordPress plugin inventories, filesystem checks, or trusted vulnerability management data.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of active exploitation. The vulnerability is remotely reachable but requires user interaction. Stored XSS can persist beyond the initial interaction and may affect later site users, depending on where the script is stored and rendered.
Researcher notes
Evidence is limited to the CVE metadata and Patchstack database reference. The bundle identifies CWE-352 and describes CSRF leading to stored XSS, but does not provide request details, vulnerable parameters, a patch version, or exploit telemetry. Avoid assuming exploitation or remediation specifics beyond vendor guidance.
Mitigation direction
- Check vendor and Patchstack guidance for fixed versions or official mitigation.
- Update Appointmind if a patched release is available from a trusted source.
- Disable or remove Appointmind where it is not business-critical.
- Restrict administrative access and review WordPress user roles.
- Prioritize sites that allow public booking or high user traffic.
Validation and detection
- Inventory WordPress sites for the Appointmind plugin.
- Confirm installed plugin versions and flag <= 4.0.0.
- Review vulnerability scanner findings against the CVE record.
- Check whether the plugin is enabled on public-facing sites.
- Look for unexpected stored content changes in affected workflows.
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-2024-51679 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
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
SSVC decision data
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:C/C:L/I:L/A:L2.83.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/Wordpress/Plugin/appointmind/vulnerability/wordpress-appointmind-plugin-4-0-0-csrf-to-stored-xss-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
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.