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

published 2026-11-12 2d ago modified 2026-11-12 2d ago also GHSA-g6f8-c3x9-jv7f

cvss: 5.4; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no EPSS score yet
public exploits: 0; none known

### 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()`.

Patch / fix

fixed in 1 links 3

packagist code16/sharp 9.23.0, 10.0.0-beta.4

github.com/code16/sharp@339f891 commit
github.com/code16/sharp#748 pull request
github.com/code16/sharp/releases/tag/v9.23.0 release

Is CVE-2026-84987 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	5.4	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
packagist	code16/sharp	<9.23.0 >=10.0.0-beta.1, <10.0.0-beta.4	9.23.0 10.0.0-beta.4

Classification

Weakness

CWE-625 Permissive Regular Expression
CWE-918 Server-Side Request Forgery

References

Sources

GitHub Advisory GHSA-g6f8-c3x9-jv7f

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.