GHSA-g6f8-c3x9-jv7f: code16/sharp: Server-side request forgery through an unanchored autocomplete endpoint check

Published Nov 12, 2026
·
Updated

Impact An authenticated attacker can call the Autocomplete API with the configured endpoint as a substring to request another server-side route.

Patches The problem has been patched in 9.23.0 and pre-release version 10.0.0-beta.4. The regex verifying the endpoint has been anchored to forbid substring injection.

Workarounds Use SharpFormAutocompleteRemoteField::setRemoteCallback() instead of SharpFormAutocompleteRemoteField::setRemoteEndpoint().

Other sources

code16/sharp: Server-side request forgery through an unanchored autocomplete endpoint check

— Packagist

Affected Software

4 affected componentsFixes available
composer/code16/sharp>=10.0.0-beta.1<10.0.0-beta.4
10.0.0-beta.4
composer/code16/sharp<9.23.0
9.23.0
composer/code16/sharp>=10.0.0-beta.1, <10.0.0-beta.4
10.0.0-beta.4
composer/code16/sharp<9.23.0
9.23.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/code16/sharp to a version that resolves this vulnerability.

    Fixed in 10.0.0-beta.4
  2. Upgrade

    Upgrade composer/code16/sharp to a version that resolves this vulnerability.

    Fixed in 9.23.0
  3. Upgrade

    Upgrade code16/sharp to a version that resolves this vulnerability.

    Fixed in 9.23.0
  4. Upgrade

    Upgrade code16/sharp to a version that resolves this vulnerability.

    Fixed in 10.0.0-beta.4
  5. Configuration

    Use SharpFormAutocompleteRemoteField::setRemoteCallback() instead of SharpFormAutocompleteRemoteField::setRemoteEndpoint().

    code16/sharp autocomplete remote callback = SharpFormAutocompleteRemoteField::setRemoteCallback()

Event History

Nov 12, 2026
Advisory Published
via GitHub·06:21 PM
Data Sourced
via GitHub·06:21 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Who can exploit this issue?

An attacker must be authenticated and able to call the Autocomplete API. Exploitation does not require user interaction.

2

Which configurations are affected?

Configurations using SharpFormAutocompleteRemoteField::setRemoteEndpoint() are affected because the endpoint validation allowed the configured endpoint to appear only as a substring. Use of setRemoteCallback() is identified as the workaround.

3

What versions contain a fix?

The issue is patched in version 9.23.0 and pre-release version 10.0.0-beta.4.

4

What can be done if upgrading is not immediately possible?

Replace SharpFormAutocompleteRemoteField::setRemoteEndpoint() with SharpFormAutocompleteRemoteField::setRemoteCallback().

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203