Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconAuthenticate as registered user
-
DeliveryAccess page editor
-
ExploitInject event handler in pageDescription field
-
InstallSubmit form to editPage function
-
C2Payload stored without sanitization
-
ExecuteVictim visits page
-
ImpactScript executes in victim's browser context
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires (1) valid authentication to LinkStack (PR:L in CVSS vector), (2) access to the editPage function with permission to modify page descriptions, and (3) victim interaction with the affected page (UI:P). The vulnerability does NOT affect unauthenticated users or those without edit permissions. Non-default configurations are not required - the vulnerability exists in default deployments where user registration and page editing are enabled. The attack is limited to stored XSS on the specific page being edited; it does not propagate site-wide unless the page description is displayed in global templates. |
| Impact | CVSS v4.0 score of 2.0 reflects the limited scope: PR:L (login required) and UI:P (user interaction needed for impact) substantially reduce real-world attack surface compared to unauthenticated network-based XSS. The CVSS vector shows VI:L (low integrity impact), appropriate for XSS affecting session cookies or sensitive page content rather than system compromise. However, EPSS data is not provided, so exploitation probability cannot be cross-referenced. The presence of publicly available exploit code (E:P in vector) and vendor acknowledgment via pull request (though unmerged at analysis time) indicate this is a recognized, demonstrable vulnerability rather than theoretical. The low CVSS score combined with public POC suggests this is primarily a concern for multi-user LinkStack deployments where authenticated users may be adversarial, rather than a critical internet-facing risk. Defense priority depends on deployment model: self-hosted instances with trusted users face minimal risk; multi-tenant or open-registration scenarios require immediate patching. |
| Exploit ScenarioDerived | An authenticated attacker with page editing privileges creates or edits a page and injects a payload such as '" onmouseover="alert(1)" data-x="' into the pageDescription field. The malicious script is stored in the database. When another user visits the page, the unescaped payload is rendered in their browser, triggering the onmouseover event and executing arbitrary JavaScript in their session context, allowing cookie theft or account hijacking. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 30, 2026
Stored cross-site scripting (XSS) in LinkStack up to version 4.8.6 allows authenticated users to inject malicious scripts via the pageDescription parameter in the editPage function, which are then stored and executed in the browsers of users viewing the affected page. The vulnerability requires user interaction (victim must view the page) and authenticated access, limiting its scope to authenticated attackers, but publicly available exploit code exists and the vendor has provided a fix via pull request #974.
RemediationAI
Upgrade LinkStack to the patched version released after pull request #974 is merged and tagged; the exact version number is not explicitly stated in references, so verify with the LinkStack project's release page or GitHub tags. If immediate upgrade is not feasible, disable the page editing feature for unprivileged users or implement a strict Content Security Policy (CSP) header with script-src 'self' to prevent inline script execution (trade-off: may break legitimate scripts if the application embeds inline JavaScript elsewhere). Additionally, implement input validation at the application level by using Laravel's built-in sanitization methods (e.g., HTMLPurifier) for rich-text fields before storage. Manual code patching is possible using the regex patterns from PR #974 lines that strip on* attributes, but this is not recommended for production without vendor verification.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
LinkStack is a PHP-based web application built with Laravel. The vulnerability exists in the UserController.php file's editPage function, which processes user-submitted page descriptions without proper output encoding or input sanitization. CWE-79 (Improper Neutralization of Input During Web Page Generation) occurs because user-controlled input from the pageDescription parameter is stored in the database and later rendered in HTML responses without adequate escaping. The fix involves two regex patterns that strip event handler attributes (on* attributes) from the input before storage, preventing inline JavaScript execution. The use of Laravel's templating should provide context-aware escaping, but the application either disables Blade escaping (using triple braces {{{ }}}) or fails to use it correctly for this field.
Know when Linkstack gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P
Primary rating from Vendor (VulDB) · only source for this CVE.
CVSS VectorVendor: VulDB
Lifecycle Timeline
4DescriptionCVE.org
A weakness has been identified in LinkStackOrg LinkStack up to 4.8.6. Impacted is the function editPage of the file app/Http/Controllers/UserController.php. Executing a manipulation of the argument pageDescription can lead to cross site scripting. It is possible to launch the attack remotely. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through a pull request but has not reacted yet.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Insufficient Session Expiration in GitHub repository linkstackorg/linkstack prior to v4.2.9. Rated critical severity (CV
Weak Password Recovery Mechanism for Forgotten Password in GitHub repository linkstackorg/linkstack prior to v4.2.9. Rat
LinkStack 2.7.9 through 4.7.7 allows resources\views\components\favicon.blade.php link SSRF. Rated medium severity (CVSS
LinkStack up to version 4.8.6 contains an authorization bypass vulnerability in the saveLink function of UserController.
Cross-site request forgery in LinkStack (linkstackorg:linkstack) affects all versions up to and including 4.8.8 and lets
EUVD-2026-26438
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB