Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister standard member account
-
DeliveryInject JS payload into cust_blurb or cust_locate fields
-
ExploitWait for administrator to view attacker profile
-
ExecutionPayload executes in admin browser session
-
ImpactExfiltrate admin session token or perform privileged actions
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) the attacker holds a valid registered member account on the target ElkArte instance (PR:L - low-privilege authenticated access); (2) the cust_blurb or cust_locate custom profile fields are enabled and writable for regular members; (3) an administrator must actively view the attacker's profile page, either through direct navigation or routine moderation (UI:R). What limits exploitation: closed-registration forums that require admin approval for new accounts significantly raise the barrier; administrators who never view individual member profiles outside of specific moderation events reduce the chance of trigger; the flaw does not enable direct server-side code execution and has no availability impact. No network-level restrictions limit the initial registration step - the forum must simply be reachable over the internet. |
| Impact | The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N) scores 5.4 (Medium), which reasonably reflects the attack requirements: a registered account (PR:L) and an administrator who views the malicious profile (UI:R). The scope change (S:C) is the distinguishing factor - impact is not confined to the attacker's own session but crosses into an administrator's session, enabling privilege escalation. No EPSS data was provided in the source intelligence, and CISA KEV status is absent, indicating no confirmed active exploitation at time of analysis. The real-world priority is moderate: open-registration forums face higher exposure because any user can weaponize the flaw, whereas invite-only or closed communities are largely protected by the PR:L prerequisite. The medium CVSS score is not an artifact of inflated ratings here - it accurately reflects that UI:R and PR:L genuinely limit blast radius compared to unauthenticated, no-interaction attacks. |
| Exploit ScenarioDerived | An attacker registers a standard member account on the target ElkArte forum and submits a JavaScript payload (e.g., a cookie-stealing script posting to an attacker-controlled endpoint) into the cust_blurb or cust_locate profile fields. When an administrator views the attacker's profile page - a routine moderation task - the unescaped script executes in the administrator's browser session, exfiltrating the admin's session token or performing privileged forum actions on their behalf. No public proof-of-concept code has been identified, but the attack technique is well-understood and trivially constructible from the description alone. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 11, 2026
Stored cross-site scripting in ElkArte Forum 2.0 Beta 1 enables any registered member to persist malicious JavaScript in the cust_blurb and cust_locate profile fields, which render unescaped when administrators view affected profiles. The scope-changing nature of the flaw (CVSS S:C) means the payload executes within an administrator's browser session, creating a realistic path to session hijacking or privilege escalation. No public exploit code or CISA KEV listing has been identified at time of analysis, but the low barrier to exploitation - any registered account suffices - makes this a meaningful risk for forums with open registration.
RemediationAI
No vendor-released patched version has been independently confirmed at time of analysis - affected versions inferred from EUVD data and the upstream GitHub repository (https://github.com/elkarte/Elkarte). Administrators should monitor the ElkArte GitHub repository for commits addressing output encoding in profile field rendering. As an immediate compensating control, disable or restrict access to the cust_blurb and cust_locate custom profile fields through the admin panel if these fields are not operationally required; this removes the injection surface entirely with no functional loss for forums that do not use them. Alternatively, restrict new member registrations or require admin approval for new accounts, raising the bar for the PR:L prerequisite. Implementing a Content Security Policy header that blocks inline script execution would significantly reduce exploitability even if the underlying encoding flaw persists, though CSP configuration complexity may introduce its own risks if misconfigured.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
ElkArte Forum (CPE: cpe:2.3:a:elkarte_forum:elkarte) is an open-source PHP-based community forum. The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation - Cross-site Scripting), specifically the stored (persistent) variant. The root cause is absent server-side output encoding: the custom profile fields cust_blurb and cust_locate accept arbitrary user input that is written directly to the database and later echoed into profile view templates without HTML entity encoding or Content Security Policy mitigation. Because profile pages are rendered for all viewers, including privileged administrators, the injected payload executes in an elevated browser context rather than the attacker's own session.
Know when Elkarte 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
AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Network-delivered stored XSS requires a registered account (PR:L) and active admin interaction (UI:R); scope change (S:C) reflects session impact crossing to administrator context with limited confidentiality and integrity effect.
Primary rating from Vendor (TuranSec).
CVSS VectorVendor: TuranSec
DescriptionCVE.org
A stored cross-site scripting vulnerability in ElkArte Forum 2.0 Beta 1 allows any registered member to inject persistent JavaScript into the profile fields cust_blurb and cust_locate. The fields are saved without HTML encoding and rendered unescaped in profile views visible to administrators. An attacker can craft a payload that executes in an administrator session, enabling session hijacking or privilege escalation.
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.
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
EUVD-2026-56023
GHSA-7g6m-7cgf-xmj8
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB