Skip to main content
Menu
CVEs

CVE

Sharp server-side request forgery in autocomplete endpoint check

CVE-2026-84987EUVD-2026-127134

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

5.4MediumCNA
Exploited
No known exploitation
Fix
Fixed in 9.23.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 9.23.0.

Published
Last modified
Reference
Last checked
8/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

code16 Sharp, a Laravel-based framework for building administrative interfaces, has a server-side request forgery flaw in its autocomplete endpoint check. A logged-in attacker who can reach the application over the network can send an autocomplete request that makes the server call a different internal route, because the check only matches part of the endpoint.

Written by a model from the sources below. Verify against them.

Original description

code16 Sharp is a Laravel-based framework for building content-management and administrative interfaces. Prior to 9.23.0, an authenticated attacker can call the autocomplete API with a request endpoint that contains the configured remote endpoint only as a substring. The endpoint validation uses an unanchored regular expression, so a different internal route can satisfy the check and be invoked server-side through the autocomplete request. The vulnerable path uses SharpFormAutocompleteRemoteField::setRemoteEndpoint(); applications using SharpFormAutocompleteRemoteField::setRemoteCallback() are not affected by this endpoint-selection flaw. This issue is fixed in version 9.23.0.

cve.now Index

8Pcve.now Index 8 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.4/10CVSS 5.4
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 if CISA's SSVC rates exploitation active
  • Would score about 27 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 9.23.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-84987 (code16/sharp: Server-side request forgery through an unanchored autocomplete endpoint check), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-84987 (entry last updated 2026-11-17):
Affected:
- code16 sharp: fixed in 9.23.0
Fixed versions: 9.23.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-84987 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-84987 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/code16/sharp/security/advisories/GHSA-g6f8-c3x9-jv7f
- https://github.com/code16/sharp/pull/748
- https://github.com/code16/sharp/commit/339f89110f36d06eaad3f2b4bd048fa5424e5558
- https://github.com/code16/sharp/releases/tag/v9.23.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-84987
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-84987"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • code16 sharp

    fixed in 9.23.0

Evidence 6

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 3

  1. Repository
  2. Repository
  3. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-84987

Is CVE-2026-84987 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-84987?

sharp: before 9.23.0.Source: cve.now feed data

How do I fix CVE-2026-84987?

Upgrade to a fixed version: 9.23.0.Source: cve.now feed data

More CVEs