CVE-2024-11833
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in PlexTrac allows arbitrary file writes.This issue affects PlexTrac: from 1.61.3 before 2.8.1.
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 confidenceA path traversal vulnerability in PlexTrac versions 1.61.3 through before 2.8.1 allows authenticated or unauthenticated attackers to write files to arbitrary locations on the filesystem by manipulating path inputs, potentially enabling remote code execution or complete system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.61.3, < 2.8.1CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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.
-
Check PlexTrac installed versionAccess the PlexTrac admin interface, typically at /admin/settings, or check the Docker container/image version with 'docker ps' and inspect the image tag. Also check the package.json or application metadata if accessible via API at /api/version.Affected if The installed version is >= 1.61.3 and < 2.8.1
-
Verify file upload functionality is exposedCheck if report uploads, evidence uploads, or any file import features are enabled in the PlexTrac settings. These endpoints typically accept file path parameters that could be manipulated.Affected if File upload, report import, or evidence upload features are enabled and accessible to users
-
Identify application write permissionsExamine the file system permissions on the PlexTrac data directory (commonly /plextrac or the mounted volume). Run 'ls -la' on the data directory and check if the application user has write access outside the intended upload directories.Affected if The PlexTrac service account has write permissions to directories outside the designated upload folder
-
Check for custom path validationReview any custom web server configuration (nginx/apache), reverse proxy settings, or application-level filters that may perform input validation on file path parameters. Look for rules that block '../' sequences.Affected if No custom input validation or path sanitization is implemented on file upload endpoints
A user is affected if their PlexTrac version is between 1.61.3 and 2.8.1 (exclusive) and the file upload or report import functionality is enabled and accessible to users.
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.
dbcve · scoped2.8.1
Upgrade PlexTrac to version 2.8.1 or later to remediate this vulnerability. If immediate upgrading is not possible, implement input validation and restrict file write permissions as compensating controls.
2.8.1 or later
- Verify current Plextrac version by accessing the admin dashboard or checking the installation
- Review the Plextrac upgrade documentation at docs.plextrac.com for version-specific upgrade procedures
- Create a complete backup of the Plextrac database and configuration files before upgrading
- Ensure system meets minimum requirements for version 2.8.1 or later
- Execute the upgrade process following Plextrac's standard upgrade procedure for your deployment method (docker, native, etc.)
- Verify the upgrade was successful and the application is functioning normally
- Confirm the new version is 2.8.1 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11833 — 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-2024-11833 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