CyberSecBulletin

Code16 vulnerabilities

We track 5 vulnerabilities in Code16 products. 5 are rated high or critical, and none are known to be exploited. The most recent was published on September 24, 2026.

5vulnerabilities
0critical
5high
0exploited
8.3average CVSS score

Latest Code16 vulnerabilities

  • 8.7 High severity

    sharp: Improper Neutralization of Input During Web Page Generation

    CVE-2026-61825Code16

    code16 Sharp is a Laravel-based framework for building content-management and administrative interfaces. Versions before 9.22.5 contain a stored cross-site scripting vulnerability in `SharpEditorFormField`: attacker-controlled content bearing the `data-html-co

  • 7.3 High severity

    sharp: Improper Neutralization of Input During Web Page Generation

    CVE-2026-61823Code16

    code16 Sharp is a Laravel-based framework for building content-management and administrative interfaces. Versions before 9.22.5 contain a stored cross-site scripting vulnerability in the rich-text editor because the HTML sanitizer permits the `srcdoc` attribut

  • 7.7 High severity

    sharp: Authorization Bypass Through User-Controlled Key

    CVE-2026-44692Code16

    Sharp 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 r

  • 8.8 High severity

    sharp: Unrestricted Upload of File with Dangerous Type

    CVE-2026-33687Code16

    Sharp is a content management framework built for Laravel as a package. Versions prior to 9.20.0 contain a vulnerability in the file upload endpoint that allows authenticated users to bypass all file type restrictions. The upload endpoint within the `ApiFormUp

  • 8.8 High severity

    sharp: Improper Limitation of a Pathname to a Restricted Directory

    CVE-2026-33686Code16

    Sharp is a content management framework built for Laravel as a package. Versions prior to 9.20.0 have a path traversal vulnerability in the FileUtil class. The application fails to sanitize file extensions properly, allowing path separators to be passed into t