VulnerabilityPublished 26 Feb 2026Updated 3 Mar 2026

CVE-2026-3263: go2ismail Asp.Net-Core-Inventory-Order-Management-System · Improper Authorization

Affects go2ismail Asp.Net-Core-Inventory-Order-Management-SystemSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

5.3Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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

Affected software

Product	Affected	Fixed in
go2ismailAsp.Net-Core-Inventory-Order-Management-System	Affected =9.20250118	Fixed in–
GitHubgo2ismail/Asp.Net-Core-Inventory-Order-Management-System`pkg:github/go2ismail/Asp.Net-Core-Inventory-Order-Management-System`Other threats	Affected =9.20250118	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official patch or update is released by the vendor, organizations should implement strict access controls around the /api/Security/ endpoint, including network segmentation and firewall rules to limit access to trusted users and systems only. Conduct thorough audits of user privileges to ensure that only necessary personnel have access to the affected system components. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious API requests that attempt to manipulate authorization parameters. Monitor logs for unusual access patterns or privilege escalation attempts related to the Security API. Consider implementing additional application-layer authorization checks or compensating controls such as multi-factor authentication for accessing sensitive API endpoints. Engage in proactive vulnerability scanning and penetration testing focused on authorization mechanisms within the system. Maintain an incident response plan to quickly address any signs of exploitation. Finally, maintain communication channels with the vendor or community for updates on patches or advisories.

Description

A vulnerability was found in go2ismail Asp.Net-Core-Inventory-Order-Management-System up to 9.20250118. Affected by this vulnerability is an unknown functionality of the file /api/Security/ of the component Security API. Performing a manipulation results in improper authorization. Remote exploitation of the attack is possible. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The improper authorization vulnerability could allow attackers with limited privileges to escalate their access or perform unauthorized actions within the inventory and order management system. This could lead to unauthorized disclosure or modification of sensitive inventory data, manipulation of order records, or disruption of normal business operations. For organizations relying on this system for supply chain, inventory tracking, or order processing, such unauthorized access could result in financial losses, operational downtime, and damage to business reputation. The medium severity score reflects a moderate risk, but the absence of vendor response and patches increases the window of exposure. If exploited in a targeted manner, attackers could leverage this vulnerability to gain footholds in enterprise environments, potentially pivoting to more critical assets. The impact is particularly significant for organizations with complex supply chains or those handling sensitive inventory data, including manufacturing, retail, and logistics sectors.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Mar 2026, 21:24 UTC

Technical details

References

Community reviews

Related threats