CVE-2026-41463
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedProjeQtor versions 7.0 through 12.4.3 contain a ZipSlip path traversal vulnerability in the plugin upload functionality that allows authenticated attackers with upload permissions to write files outside the intended extraction directory by crafting ZIP archives with directory traversal sequences. Attackers can exploit unvalidated archive extraction to write a PHP webshell to a web-accessible directory and achieve remote code execution with the privileges of the web server process.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceProjeQtor versions 7.0-12.4.3 suffer from a ZipSlip path traversal vulnerability in the plugin upload functionality. The application fails to validate file paths within uploaded ZIP archives before extraction, allowing authenticated attackers with upload permissions to use directory traversal sequences (e.g., ../../../') to write arbitrary PHP files to web-accessible directories and achieve remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify ProjeQtor installation and versionLocate the ProjeQtor installation directory and find the version file (typically version.php or similar in the main ProjeQtor directory). Read the version number from this file.Affected if The installed version falls within the affected range and the plugin upload feature is accessible to the user.
-
Verify plugin upload functionality is enabledCheck if the plugin upload feature is available in the ProjeQtor web interface. Look for a plugin manager or upload section under the administration or tools menu. Confirm whether the current user account has upload permissions.Affected if Plugin upload functionality is enabled and accessible to authenticated users.
-
Inspect upload directory permissions and locationExamine the plugin upload directory configuration in ProjeQtor (typically found in config files or the tool/include directory). Verify that the upload directory is NOT within the web root or that proper .htaccess restrictions are in place.Affected if The upload directory is within the web-accessible document root without proper access restrictions.
-
Check for unexpected files in web-accessible directoriesSearch web-accessible directories (such as www, html, htdocs, or the ProjeQtor root if web-accessible) for PHP files that were not part of the original installation. Look for files with suspicious names or recent modification dates.Affected if Unexpected PHP files exist in web-accessible directories, especially those with names like shell.php, cmd.php, or similar webshell patterns.
-
Review recent upload activity logsExamine ProjeQtor's audit logs or upload history for recent plugin uploads. Look for ZIP archives that may have been uploaded and extracted. Check if any extraction occurred outside the intended plugin directory.Affected if Recent plugin uploads show evidence of files being extracted outside the designated plugin directory.
A user is affected if they run a ProjeQtor version within the affected range, have the plugin upload feature enabled for untrusted users, and either find suspicious files in web directories or observe extraction occurring outside the intended plugin directory.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade ProjeQtor to a version beyond 12.4.3 that includes proper path validation and sandboxing for extracted archive contents. Until a patch is available, restrict plugin upload permissions to only highly trusted administrators and implement web-server-level controls to prevent execution of uploaded files in plugin directories.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41463 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41463 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data