VulnerabilityPublished 14 Nov 2024Updated 20 Nov 2024

CVE-2024-50968: A business logic vulnerability exists in the Add to Cart function of itsourcecode Agri-Trading Online

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-50968, organizations should immediately implement strict input validation on the 'quant' parameter to reject negative, zero, or otherwise invalid quantity values before processing. Business logic should be revised to ensure that total price calculations cannot be manipulated by malformed inputs, including adding server-side checks that enforce minimum quantity constraints and verify total price consistency. Until an official patch is released, consider implementing web application firewall (WAF) rules to detect and block requests containing suspicious quantity values such as '-0'. Conduct thorough code reviews and testing of the checkout and cart modules to identify and fix similar logic flaws. Monitor transaction logs for anomalous patterns indicative of exploitation attempts, such as zero-value orders or unusual quantity inputs. Engage with the vendor or development team to prioritize a security patch and apply it promptly once available. Additionally, limit exposure by restricting access to the shopping system to trusted networks if feasible and educate staff on recognizing potential fraud indicators.

Description

A business logic vulnerability exists in the Add to Cart function of itsourcecode Agri-Trading Online Shopping System 1.0, which allows remote attackers to manipulate the quant parameter when adding a product to the cart. By setting the quantity value to -0, an attacker can exploit a flaw in the application's total price calculation logic. This vulnerability causes the total price to be reduced to zero, allowing the attacker to add items to the cart and proceed to checkout.

Impact

The primary impact of CVE-2024-50968 is financial fraud due to unauthorized free purchases, which undermines the integrity of the e-commerce transaction process. Organizations operating the affected Agri-Trading Online Shopping System risk direct revenue loss as attackers can exploit the flaw to obtain goods without payment. This can also damage customer trust and brand reputation if exploited at scale. The vulnerability does not compromise customer data confidentiality or system availability, but the financial and operational consequences can be severe. Attackers can automate exploitation remotely without authentication, increasing the likelihood of widespread abuse. For businesses relying heavily on this platform, the vulnerability could disrupt normal sales operations and require costly incident response and remediation efforts. Additionally, if exploited by organized fraud rings, it could lead to significant inventory depletion and financial exposure. The lack of a patch increases the urgency for organizations to apply compensating controls to mitigate risk.

References

github.com/Akhlak2511/CVE-2024-50968 (opens in a new tab)

Community reviews

Loading reviews…