CVE-2026-23797: OpenSolution Quick.Cart · Plaintext Storage of a Password
Affects OpenSolution Quick.CartSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Feb 2026
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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenSolutionQuick.Cart | Affected
| Fixed in– |
AI-suggested
European organizations using Quick.Cart 6.7 should immediately audit their installations to confirm the presence of this vulnerability. Passwords stored in plaintext should be migrated to a secure hashing algorithm (e.g., bcrypt, Argon2) as soon as possible, which may require custom development or vendor engagement. Regularly review and rotate administrative credentials and encourage users to change passwords, especially if there is suspicion of compromise. Network segmentation and logging should be enhanced to detect and prevent lateral movement by attackers who gain high privileges. Organizations should also engage with OpenSolution for updates and consider alternative e-commerce platforms if remediation is delayed.
Description
In Quick.Cart user passwords are stored in plaintext form. An attacker with high privileges can display users' password in user editing page. The vendor was notified early about this vulnerability, but didn't respond with the details of vulnerability or vulnerable version range. Only version 6.7 was tested and confirmed as vulnerable, other versions were not tested and might also be vulnerable.