Security readout for executives and security teams
Plain-English summary
Sparkshop v1.16 has a payment-flow logic flaw that can let an unauthenticated remote attacker change product quantities. The business risk is order integrity: purchases or inventory transactions may not reflect intended quantities. The CVE is rated high because exploitation is network-accessible and does not require login or user interaction.
Executive priority
Treat as high priority for any internet-facing Sparkshop v1.16 commerce deployment. The likely business impact is transaction manipulation rather than data theft or outage. If Sparkshop is not used, no direct action is needed beyond confirming asset inventory.
Technical view
CVE-2024-46307 is described as a CWE-841 improper enforcement of behavioral workflow in Sparkshop v1.16 payment logic. CVSS 3.1 is 7.5: AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. The impact is integrity only, centered on arbitrary modification of product numbers during payment flow.
Likely exposure
Organizations running Sparkshop v1.16 are the indicated exposure. The CVE record’s structured affected-product fields are incomplete, so confirm deployment details against your asset inventory and the upstream Sparkshop project.
Exploitation context
The CVSS vector indicates remote, low-complexity exploitation without authentication or user interaction. CISA KEV status is false in the provided data, and the sources do not state active exploitation. A public GitHub reference is listed by the CVE record, but exploit status is not independently confirmed here.
Researcher notes
Public metadata is sparse. The CVE names Sparkshop v1.16 and describes payment logic allowing product-number modification, but the CNA affected fields are listed as n/a. No KEV listing or active exploitation evidence is provided. Validate against upstream code and referenced disclosure without assuming broader version impact.
Mitigation direction
- Check Sparkshop upstream guidance and release history for a fix or security notice.
- Prioritize upgrading or replacing Sparkshop v1.16 if vendor guidance identifies a corrected version.
- Apply server-side validation of quantities and payment totals if you maintain custom code.
- Increase monitoring for abnormal order quantities, payment totals, and inventory changes.
- Restrict administrative and payment-related interfaces to trusted networks where feasible.
Validation and detection
- Confirm whether Sparkshop v1.16 is present in production, staging, or customer-facing environments.
- Review order workflows for server-side enforcement of product quantity and payment total integrity.
- Check logs for suspicious quantity changes around checkout or payment confirmation.
- Verify whether upstream Sparkshop has published relevant patches, commits, or advisories.
- Document compensating controls if immediate upgrade guidance is unavailable.
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-841: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-46307 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.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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.
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:N/S:U/C:N/I:H/A:N3.93.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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://gitee.com/sparkshop/sparkshopCVE reference, mitre
- https://github.com/Yllxx03/CVE/tree/main/CVE-2024-46307CVE reference, mitre
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.
Improper Enforcement of Behavioral Workflow
Improper Enforcement of Behavioral Workflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.