Skip to content

Sharp Missing Authorization Check in Quick Creation Command Endpoints

Moderate severity GitHub Reviewed Published Jun 1, 2026 in code16/sharp • Updated Jul 8, 2026

Package

composer code16/sharp (Composer)

Affected versions

>= 9.0.0, < 9.22.3

Patched versions

9.22.3

Description

Impact

The create and store endpoints of the Quick Creation Command feature did not enforce any authorization check. An authenticated Sharp user without create permission on a given entity could bypass the authorization layer and either retrieve the creation form or submit new records for that entity, as long as it had a Quick Creation Command handler configured.

Patches

Yes. The fix is included in version 9.22.3. Users should upgrade to that version or later.

Workarounds

Remove or disable Quick Creation Command handlers (quickCreationCommandHandler()) on any entity list where unauthorized access is a concern, until an upgrade is possible.

Resources

PR #729

References

@dvlpp dvlpp published to code16/sharp Jun 1, 2026
Published by the National Vulnerability Database Jun 10, 2026
Published to the GitHub Advisory Database Jul 8, 2026
Reviewed Jul 8, 2026
Last updated Jul 8, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(12th percentile)

Weaknesses

Missing Authorization

The product does not perform an authorization check when an actor attempts to access a resource or perform an action. Learn more on MITRE.

CVE ID

CVE-2026-53634

GHSA ID

GHSA-vmwx-m75v-qvch

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.