Skip to main content
Mallory
MediumVulnerability

CVE-2026-41874: Plaintext Admin Credentials in OpenSolution Quick.Cart

Published Jul 28, 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.8Medium · v4
EPSS0.18%8th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Opensolution
IdentifiersCVE-2026-41874CWE-256 · Plaintext Storage of a Password

CVE-2026-41874 is a plaintext password storage vulnerability in OpenSolution Quick.Cart. The application stores hard-coded administrator credentials in plaintext within a configuration file, exposing sensitive authentication material to anyone who can read the underlying server files. Version 6.7 was explicitly tested, and all versions are considered vulnerable. Because the credentials are embedded and stored without protection, compromise of filesystem confidentiality can directly disclose administrative authentication details and enable subsequent unauthorized administrative access.

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.

Successful exploitation exposes administrator credentials in cleartext. An attacker who obtains read access to the affected server filesystem can recover those credentials and use them to authenticate as an administrator, resulting in unauthorized access and potential privilege escalation within the Quick.Cart application. The issue also increases the blast radius of any separate local file disclosure, backup exposure, hosting compromise, or administrative misconfiguration that permits access to configuration files.

Mitigation

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

Apply strict least-privilege controls to the host and application files so that only trusted administrators and required service accounts can read configuration data. Harden the server to reduce the likelihood of local file access, monitor for unauthorized access to application configuration and backups, segregate hosting environments, and minimize exposure of administrative interfaces. Because all versions should be treated as vulnerable and no vendor patch is expected, compensating controls around filesystem confidentiality and credential rotation are the primary mitigation measures.

Remediation

Patch, then assume compromise.

No vendor fix is planned according to the available information. Remediation therefore requires operator-side changes: remove or replace deployments that rely on hard-coded plaintext administrator credentials, rotate any administrator passwords that may have been exposed, review whether the same credentials were reused elsewhere, and restrict access to configuration storage. If source modification or compensating engineering controls are feasible, credentials should be eliminated from static configuration files or replaced with securely stored secrets using appropriate hashing or secret-management mechanisms where applicable.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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-41874 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-41874 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-41874?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-41874.
Is there a patch for CVE-2026-41874?
No vendor fix is planned according to the available information. Remediation therefore requires operator-side changes: remove or replace deployments that rely on hard-coded plaintext administrator credentials, rotate any administrator passwords that may have been exposed, review whether the same credentials were reused elsewhere, and restrict access to configuration storage.
What products are affected by CVE-2026-41874?
Opensolution Quick.Cart.
How severe is CVE-2026-41874?
CVE-2026-41874 has a CVSS v4 score of 6.8 (Medium) and an EPSS score of 0.18% (8th percentile) as of Sep 25, 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.