CVE-2026-30574
Senior-Walter Web-Based Pharmacy Product Management System 1.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NSummary
CVE-2026-30574 is a high-severity Improper Enforcement of Behavioral Workflow (CWE-841) vulnerability in Senior-Walter Web-Based Pharmacy Product Management System. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique External Remote Services (T1133); ranked at the 17th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and IA-11 (Re-authentication) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-30574 is a business logic vulnerability in the SourceCodester Pharmacy Product Management System 1.0, specifically within the add-sales.php file. The application does not verify whether the requested sales quantity parameter (txtqty) exceeds the available stock level for a product. This flaw, classified under CWE-841 (Improper Enforcement of Behavioral Workflow), carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) and was published on 2026-03-27.
The vulnerability can be exploited remotely by unauthenticated attackers over the network with low complexity and no user interaction required. By manipulating the txtqty parameter in a sales request, an attacker can purchase a quantity significantly higher than the actual available stock, enabling overselling scenarios that disrupt inventory management and potentially lead to financial or operational impacts through integrity violations.
A proof-of-concept demonstrating the overselling logic flaw is available at https://github.com/meifukun/Web-Security-PoCs/blob/main/Pharmacy-Product-Management-System/Logic-AddSales-Overselling.md. No official advisories or patches are referenced in the available information.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-16706
Vulnerability Data
A Business Logic vulnerability exists in SourceCodester Pharmacy Product Management System 1.0 in the add-sales.php file. The application fails to verify if the requested sales quantity (txtqty) exceeds the available stock level. An attacker can manipulate the request to purchase…
more
a quantity that is significantly higher than the actual available stock.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V7.2.1
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement can require each successive workflow step to present the proper authorization context before proceeding.
Re-authentication requirements can be placed at critical workflow steps to ensure the actor has performed prior behaviors.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure development practices directly address proper workflow enforcement during design and coding.
Enforcing authorization policies can include sequence constraints on multi-step actions.
Hardened configuration baselines can embed required workflow ordering rules.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect workflow bypasses but does not enforce them at runtime.
Secure development lifecycle requires explicit workflow enforcement in multi-step processes.
Application security requirements include sequencing and state-transition rules for critical workflows.
Secure architecture principles address proper ordering of security-critical operations.
Secure coding practices can prevent missing workflow checks but do not define the control itself.
Change management can require workflow adherence for changes but is not the primary mitigation.