Security readout for executives and security teams
Plain-English summary
CVE-2024-51648 affects the WordPress e-shops plugin package e-shops-cart2 through version 1.0.3. A malicious site could trick a user into making a request that reflects script content in the victim's browser. Business risk depends on whether the plugin is installed and reachable.
Executive priority
Handle as a high-priority WordPress plugin exposure, especially for customer-facing sites. The issue can affect user trust and session integrity, but urgency should be asset-driven because the sources do not confirm active exploitation or provide a named patch.
Technical view
The source describes a CSRF issue in hands01 e-shops/e-shops-cart2 that allows reflected XSS. CVSS 3.1 is 7.1 high, with network attack vector, low complexity, no privileges, required user interaction, and changed scope. The provided evidence does not name a patched version.
Likely exposure
Exposure is limited to WordPress sites running the hands01 e-shops plugin package e-shops-cart2 at version 1.0.3 or earlier. Sites without this plugin are not indicated as affected by the provided sources.
Exploitation context
The bundle does not show CISA KEV listing or cite confirmed active exploitation. Successful abuse requires user interaction, consistent with CSRF and reflected XSS risk. Treat public WordPress deployments as higher priority because attackers can target users through crafted links or pages.
Researcher notes
Evidence is thin beyond the CVE metadata and Patchstack entry. The affected range is described as through 1.0.3, while the affected object metadata is sparse. Validate against installed plugin metadata before declaring exposure.
Mitigation direction
Inventory WordPress sites for e-shops/e-shops-cart2 version 1.0.3 or earlier.
Check vendor and Patchstack guidance for a fixed version or official mitigation.
Disable or remove the plugin where it is not business-critical.
Prioritize update or replacement once a safe vendor-supported version is identified.
Review compensating controls for suspicious cross-site requests and script-like parameters.
Validation and detection
Confirm whether the plugin is installed, active, and externally reachable.
Record exact plugin version across production, staging, and backups.
Review web logs for unusual requests involving plugin endpoints or reflected script-like input.
Verify no CISA KEV evidence is present in the provided bundle.
Track remediation status against each affected WordPress asset.
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.
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.
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.
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.