Skip to main content
Menu
CVEs

WebKul QloApps path traversal in archive import

CVE-2026-133479EUVD-2026-130825GHSA-J6WF-753P-3VVVPublished November 20, 2026, updated

5.1MediumCNA
Exploited
Proof of concept public, per CISA
Fix
No fix listed
Who is exposed
Not reported

Summary

WebKul QloApps has a path traversal flaw in its Archive Import feature that lets an attacker manipulate file paths and access locations outside the intended directory. An attacker can reach it remotely over the network, but only after logging in with high-level privileges.

Written by a model

Original description

A vulnerability was detected in WebKul QloApps up to 1.8.0. Affected by this vulnerability is the function postProcessDownload/installTheme of the file controllers/admin/AdminModulesController.php of the component Archive Import. The manipulation results in path traversal. It is possible to launch the attack remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133479 (WebKul QloApps Archive Import AdminModulesController.php installTheme path traversal), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133479 (entry last updated 2026-11-20):
Affected:
- WebKul QloApps: versions 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133479 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133479 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://vuldb.com/vuln/440881
- https://vuldb.com/vuln/440881/cti
- https://vuldb.com/cve/CVE-2026-133479
- https://vuldb.com/submit/1048506
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133479
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133479"}.

Affected versions

cve.now Index

28Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.1/10CVSS 5.1
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 47 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 7

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133479
RecordNVD · CVE-2026-133479
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
Exploithackmd.io · @leediay/BJ9Qd-Tvfe
Other links 4
AdvisoryVulDB · Advisory #440881
AdvisoryVulDB · Threat intelligence #440881
AdvisoryVulDB · CVE-2026-133479 record
AdvisoryVulDB · Submission #1048506

Questions about CVE-2026-133479

Is CVE-2026-133479 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133479?

QloApps: versions 1.0, 1.1, 1.2, 1.3, 1.4 and 4 more.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.