Lara Dashboard through 1.3.1 contains a server-side request forgery vulnerability in the POST /api/admin/builder/markdown/fetch endpoint that allows… (CVE-2026-87821)
Source GCVE Database
Not known to be exploited · CVSS 7.1 High.
Data as of 10/25/2026, 04:40:14 UTC
- Exploitation
Not in CISA KEV, no exploitation reported
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:NWhat to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHublaradashboard/laradashboardpkg:github/laradashboard/laradashboardOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until an official fix is available, restrict access to the vulnerable endpoint to trusted users only and monitor for suspicious activity involving the POST /api/admin/builder/markdown/fetch endpoint.
Description
Lara Dashboard versions through 1.3.1 have a server-side request forgery (SSRF) vulnerability in the POST /api/admin/builder/markdown/fetch endpoint. This flaw allows any authenticated user to fetch arbitrary URLs and read the response body without host validation or redirect restrictions. Exploitation can lead to reading internal HTTP services and cloud metadata, including IAM credentials.
Impact
An attacker with authentication can exploit this SSRF vulnerability to read arbitrary URLs from the server side, including internal HTTP services and cloud metadata endpoints. This can lead to disclosure of sensitive information such as IAM credentials, which may facilitate further compromise of the environment.
Weaknesses
- CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
References
- github.com/laradashboard/laradashboard/security/advisories/GHSA-4xqv-4c27-6c4j (opens in a new tab)
- github.com/laradashboard/laradashboard/security/advisories/GHSA-f36j-h77g-6wj8 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-87821 (opens in a new tab)
- github.com/laradashboard/laradashboard/commit/738cc1a219ce459323ef1d09c3789075f1b8d2f2 (opens in a new tab)
- github.com/laradashboard/laradashboard (opens in a new tab)
- github.com/laradashboard/laradashboard/blob/v0.9.2/app/Services/Builder/MarkdownFetchService.php (opens in a new tab)
- github.com/laradashboard/laradashboard/blob/v1.3.1/app/Http/Controllers/Api/Builder/MarkdownController.php (opens in a new tab)
- github.com/laradashboard/laradashboard/blob/v1.3.1/app/Services/Builder/MarkdownFetchService.php (opens in a new tab)
- github.com/laradashboard/laradashboard/blob/v1.3.2/app/Support/Security/SafeUrlValidator.php (opens in a new tab)
- github.com/laradashboard/laradashboard/releases/tag/v1.3.2 (opens in a new tab)
- vulncheck.com/advisories/lara-dashboard-0.9.2-through-1.3.1-server-side-request-forgery-in-builder-markdown-fetch (opens in a new tab)