CVE-2026-41875: OpenSolution Quick.Cart · Cross-Site Request Forgery (CSRF)
Affects OpenSolution Quick.CartSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium · fixed in 6.7.1 : update OpenSolution Quick.Cart when convenient.
Data as of 12 Nov 2026, 23:24 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.7.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenSolutionQuick.Cart | Affected
| Fixed in– |
AI-suggested
A patch fixing this vulnerability was released in Quick.Cart version 6.7.1 on November 9, 2026. Deployments should upgrade to version 6.7.1 or later to remediate this issue. Until patched, administrators should avoid visiting untrusted websites while logged into the admin panel to reduce risk.
Description
Quick.Cart is vulnerable to Cross-Site Request Forgery in admin config panel. Malicious attacker can craft special website, which when visited by the admin, will automatically send a POST request that changes admin's login and password. This software does implement simple protection against this type of attack, but it is easily bypassed by manipulating the referer header. All forms available in this software are potentially vulnerable. This issue was fixed in a patch to version 6.7 published on 09.11.2026, deployments without this patch are still vulnerable