CVE-2019-17399
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 · uneditedThe Shack Forms Pro extension before 4.0.32 for Joomla! allows path traversal via a file attachment.
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 confidenceThe Shack Forms Pro extension for Joomla! before version 4.0.32 contains a path traversal vulnerability that allows attackers to use directory traversal sequences (../../) within file attachment parameters to access files outside the intended web root directory, potentially exposing sensitive system files.
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< 4.0.32CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check Shack Forms Pro versionIn the Joomla administrator panel, go to Extensions > Manage > Manage and search for Shack Forms Pro to view the installed version numberAffected if The installed version is any version before 4.0.32
-
Verify file attachment feature is enabledAccess the Shack Forms Pro component in Joomla admin and review the form configurations to determine if any forms have file upload fields enabledAffected if File attachment fields are enabled in any active form configuration
-
Inspect file upload parameter handlingIf file upload fields are in use, examine the HTTP requests when submitting forms with file attachments to check if the application processes file path parameters that could contain directory traversal sequencesAffected if File path parameters in the upload functionality accept unsanitized directory traversal sequences without proper validation
The environment is affected if Shack Forms Pro version is below 4.0.32 AND file attachment fields are configured in any form, since the path traversal vulnerability exists in the file attachment parameter handling of vulnerable versions.
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 · scoped4.0.32
Upgrade Shack Forms Pro extension to version 4.0.32 or later, which contains the patch fixing the path traversal vulnerability in file attachment handling.
Shack Forms Pro 4.0.32 or later
- 1. Create a full backup of your Joomla! site including database and files
- 2. Navigate to the Joomlashack website and download Shack Forms Pro version 4.0.32 or later
- 3. Log in to your Joomla! administrator dashboard
- 4. Go to Extensions > Manage > Install
- 5. Upload and install the updated Shack Forms Pro extension package
- 6. After installation, verify the version number in Extensions > Manage to confirm 4.0.32 or higher is installed
- 7. Test file attachment functionality to ensure the form still works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17399 — 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-2019-17399 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