CVE-2026-44692
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 · uneditedSharp is a content management framework built for Laravel as a package. Prior to version 9.22.0, Sharp exposes a generic download endpoint that authorizes access only to the supplied Sharp entity instance, but then reads the target storage disk and path from request parameters. Because the requested storage object is not bound to the authorized entity instance, an authenticated Sharp user who can view one valid record may use that record as an authorization anchor to download unrelated disk-relative objects from configured Laravel Storage disks. The confirmed impact is authenticated disclosure of unrelated objects from configured Laravel Storage disks. This issue does not imply arbitrary host filesystem access outside configured Laravel Storage disk roots. This issue has been patched in version 9.22.0.
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 · moderate confidenceSharp CMS has an IDOR vulnerability in its download endpoint where authorization checks the Sharp entity instance but then reads the storage disk and path directly from request parameters. Since the storage object is not bound to the authorized entity, an authenticated user who can view one record can download arbitrary files from configured Laravel Storage disks.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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.
-
Identify installed Sharp versionLocate the Sharp package in your project's composer.json or composer.lock file and extract the installed version numberAffected if The installed version is lower than 9.22.0
-
Verify Sharp is present in the projectCheck for the Code16/Sharp package in your vendor directory or dependency listAffected if Sharp is installed and the version cannot be determined or is below 9.22.0
-
Confirm download endpoint existsInspect Sharp's route definitions (typically in routes/vendor.php or the application routes) for a download route that handles file retrievalAffected if A download endpoint accepting disk and file path parameters is accessible to authenticated Sharp users
-
Check authentication configuration for SharpReview the auth.php configuration and Sharp's authentication middleware setup to determine which authenticated users can access Sharp functionsAffected if Authenticated users with limited record access can reach Sharp endpoints
-
Verify storage disk configurationExamine the Laravel storage configuration (config/filesystems.php) to identify available disks and their access pathsAffected if Disks are configured that could allow file system access beyond intended boundaries
A user is affected if Sharp version is below 9.22.0 AND they have any authenticated access to Sharp records, as the download endpoint can be exploited to retrieve arbitrary files from configured storage disks.
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 · scopedUpgrade to Sharp version 9.22.0 or later, which patches the authorization binding issue.
Sharp version 9.22.0
- Update the Sharp package to version 9.22.0 or later by running: composer require code16/sharp:^9.22.0
- After upgrading, verify the fix by testing that the download endpoint now properly validates the storage object is bound to the authorized entity
- Review any custom file upload or download handlers in your Sharp implementation to ensure they do not introduce similar IDOR vulnerabilities
- Audit configured Laravel Storage disks to ensure they do not contain sensitive files that could be exposed if other IDOR issues exist
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44692 — 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-44692 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