A vulnerability was found in Bdtask Multi-Store Inventory Management System 1.0. The impacted element is the function accounts_report_search of the file application/modules/accounts/controllers/Accounts.php of the component Accounts Report Handler. Performing a manipulation of the argument dtpToDate results in sql injection. The attack is possible to be carried out remotely. The exploit has been made public and could be used.
Security readout for executives and security teams
Plain-English summary
CVE-2026-10155 is a remotely reachable SQL injection in Bdtask Multi-Store Inventory Management System 1.0. A logged-in user could manipulate the Accounts Report date parameter to affect database queries, risking exposure, alteration, or disruption of inventory and accounting data.
Executive priority
Treat this as a moderate-priority application security issue. It targets accounting/reporting data and has public exploit material, but current evidence indicates authentication is required and does not confirm active exploitation.
Technical view
The issue affects accounts_report_search in application/modules/accounts/controllers/Accounts.php, specifically the dtpToDate argument in the Accounts Report Handler. It is classified as CWE-89/CWE-74 with CVSS v2 5.8, network reachable, low complexity, and requiring authentication. Public proof-of-concept material is referenced.
Likely exposure
Exposure appears limited to organizations running Bdtask Multi-Store Inventory Management System 1.0 with the Accounts Report feature reachable by authenticated users. No other versions or products are identified in the provided sources.
Exploitation context
A public exploit is referenced, but the CVE is not listed as KEV and the provided sources do not show confirmed active exploitation. Authentication is required under the supplied CVSS vector, reducing broad internet-scale risk but still relevant for compromised or low-privilege accounts.
Researcher notes
The strongest evidence is the CVE/VulDB description naming the controller, function, component, and parameter. Remediation details are incomplete in the supplied sources, so avoid assuming a patch exists. Focus validation on authenticated report access, SQL construction around dtpToDate, and compensating access controls.
Mitigation direction
Identify any Bdtask Multi-Store Inventory Management System 1.0 deployments.
Restrict Accounts Report access to trusted, necessary users only.
Check Bdtask or VulDB guidance for an official fix or workaround.
Monitor application and database logs for unusual Accounts Report activity.
Review database integrity if suspicious report queries are found.
Validation and detection
Confirm whether version 1.0 is deployed in production or staging.
Verify whether Accounts Report is reachable by authenticated users.
Review handling of the dtpToDate parameter for unsafe SQL construction.
Check logs for database errors or unusual report searches.
Track CVE, VulDB, and vendor pages for remediation updates.
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 · low confidence lookup
CWE-74: 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.
Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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.