Skip to main content
Mallory
MediumVulnerability

CVE-2026-63303: Path Traversal in OpenSolution Quick.CMS

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.
CVSS5.1Medium · v4
EPSS0.57%48th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-63303CWE-23 · Relative Path Traversal

CVE-2026-63303 is a relative path traversal vulnerability affecting OpenSolution Quick.CMS, reported as affecting versions through 6.8.0. The flaw is present in handling of the URI path component of HTTP requests: the application fails to properly normalize dot-dot-slash traversal sequences before resolving and serving the requested resource. As a result, an authenticated attacker with administrative privileges can submit a crafted request containing traversal sequences and cause the application to read files outside the intended webroot scope, specifically from a sibling directory of the webroot.

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 allows an authenticated administrator to read the contents of files outside the intended document root boundary. The disclosed data may include sensitive application or server-side information stored in directories adjacent to the webroot, potentially aiding further compromise, reconnaissance, or exposure of confidential information. The available information indicates file-read impact rather than code execution or privilege escalation.

Mitigation

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

Restrict access to the administrative interface to trusted users and networks only, and minimize exposure of administrative functionality to the public internet. Apply web-server or reverse-proxy rules that reject requests containing traversal patterns in the URI path, and harden filesystem layout so sensitive files are not stored in directories adjacent to the webroot where they could be exposed through path traversal. Monitoring for suspicious requests containing traversal sequences can also help detect exploitation attempts.

Remediation

Patch, then assume compromise.

No vendor fix was planned according to the available information, as the vendor assessed the likelihood of exploitation as very low. A proper remediation would require server-side canonicalization and validation of request paths before file resolution, ensuring traversal sequences cannot escape the intended content directory. Affected deployments should review whether an updated vendor release becomes available and, if not, consider local code changes or compensating controls.

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.
FAQ

Frequently asked questions

Is CVE-2026-63303 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-63303 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-63303?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-63303.
Is there a patch for CVE-2026-63303?
No vendor fix was planned according to the available information, as the vendor assessed the likelihood of exploitation as very low. A proper remediation would require server-side canonicalization and validation of request paths before file resolution, ensuring traversal sequences cannot escape the intended content directory.
How severe is CVE-2026-63303?
CVE-2026-63303 has a CVSS v4 score of 5.1 (Medium) and an EPSS score of 0.57% (48th 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.