Quick answers
- Is CVE-2026-86669 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86669 being exploited in the wild.
- How severe is CVE-2026-86669?
- High severity, with a CVSS score of 7.3, published 8 September 2026.
- Which products and versions are affected?
- Aircheng-Org iWebShop-5 up to 5.15.
- Is there a fix for CVE-2026-86669?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-86669 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-86669?
- Check whether you run Aircheng-Org iWebShop-5 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authentication bypass (CWE-287) in the seller login function (controllers/systemseller.php). The root cause is improper SQL operator precedence: the query checks `seller_name = "..." OR mobile = "..." AND is_del = 0 AND is_lock = 0`, where the AND conditions bind only to the mobile branch due to operator precedence, allowing sellers with `is_lock = 1` to authenticate via username. Attack vector is network-based and requires valid seller credentials. An attacker with a locked seller account can POST to the login endpoint and gain full seller panel access. The fix requires rewriting the SQL predicate with explicit parentheses and/or PHP-level validation of the lock status after fetching the seller record.
Affected products
- aircheng-org iWebShop-5 up to 5.15
Timeline
- 2026-07-29: disclosed: Vulnerability reported via GitHub issue #6
- 2026-09-08: advisory: CVE-2026-86669 published on NVD
- 2026-09-08: other: Exploit is public; project has not responded to issue report