Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-41875: CSRF in Quick.Cart Administrative Configuration Panel

Published Sep 29, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.9Medium · v4
EPSS0.17%6th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Opensolution
IdentifiersCVE-2026-41875CWE-352 · Cross-Site Request Forgery (CSRF)

CVE-2026-41875 is a cross-site request forgery vulnerability in the OpenSolution Quick.Cart administrative configuration panel. A malicious website can cause an authenticated administrator who visits it to submit a POST request that changes the administrator login and password. Quick.Cart's existing Referer-header-based CSRF protection can be bypassed through Referer-header manipulation. Other Quick.Cart forms may also be susceptible to CSRF.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker can change an administrator's login credentials without the administrator intentionally submitting the administrative request. This can result in administrative account takeover and full compromise of the Quick.Cart administration interface.

Mitigation

If you can’t patch tonight, do this now.

Until a verified patched release is installed, restrict the administration interface to trusted networks or VPN users, enforce strong external access controls, and monitor for unauthorized administrator-account and configuration changes. Do not rely solely on Referer-header validation for CSRF protection.

Remediation

Patch, then assume compromise.

Apply the vendor-supplied patch. Version information is inconsistent: the vulnerability is described as affecting versions through 6.7.0, while remediation guidance says to update to Quick.Cart 6.7 or later and separately describes a patch to version 6.7. Confirm the patched build with the vendor before deployment.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
CVE-2026-41875-EXPLOIT-QuickCart-one-click-Account-TakeoverThe repository contains README.md (8,140 bytes) and a standalone exploit.py (10,108 bytes). The Python script uses standard-library components to generate and host an HTML CSRF page; embedded JavaScript submits a hidden configuration form automatically. The attack relies on an authenticated administrator visiting that page and the target accepting a request without a Referer header. Form fields replace administrative credentials and also set numerous store options, including language, currency, page identifiers, and file-cleanup settings, creating a risk of unintended configuration changes. Optional --xss mode supplies a hardcoded title-breaking alert(1) payload; other JavaScript requires editing XSS_PAYLOAD. The README attributes the CSRF to CVE-2026-41875 and says the stored-XSS behavior has no assigned CVE, but these claims are not independently verified. This is exploit code rather than a detection tool, with no visible evidence of a fake exploit, reverse shell, or exfiltration. The supplied Python content is truncated through the HTML-building, server, and argument-handling portions, so complete syntax, escaping, binding behavior, and runtime functionality cannot be confirmed. No automated exploitation-success check is visible. Repository URL, revision, and archive size were not provided; empty strings and zero represent unavailable metadata, not an empty repository.hhg69 · Disclosed Oct 5, 2026 · python · html · web · browser · networkOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
OpensolutionQuick.Cartapplication
FAQ

Frequently asked questions

Is CVE-2026-41875 exploited in the wild?
As of Sep 30, 2026, Mallory has no reports of CVE-2026-41875 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-41875?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-41875, the earliest disclosed Oct 5, 2026.
Is there a patch for CVE-2026-41875?
Apply the vendor-supplied patch. Version information is inconsistent: the vulnerability is described as affecting versions through 6.7.0, while remediation guidance says to update to Quick.Cart 6.7 or later and separately describes a patch to version 6.7.
What products are affected by CVE-2026-41875?
Opensolution Quick.Cart.
How severe is CVE-2026-41875?
CVE-2026-41875 has a CVSS v4 score of 6.9 (Medium) and an EPSS score of 0.17% (6th percentile) as of Sep 30, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.