CVE-2026-26211: Ekushey Project Manager CRM 5.0 Stored XSS via System Name Field

Published Aug 25, 2026

Updated

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.

Affected Software

1 affected component

Ekushey Project Manager CRM=5.0

Event History

Aug 25, 2026

CVE Published

via MITRE·05:28 PM

Data Sourced

via MITRE·05:28 PM

DescriptionSeverityWeakness

Frequently Asked Questions

Who can trigger the stored payload, and who is exposed to it?

An attacker needs an administrator session to set the system name. Once stored, the payload runs for every visitor loading the unauthenticated login page, including users who are not signed in.

Does exploitation require a victim to authenticate or interact with the page?

No authentication is required for the victim because the affected login page is publicly served. The payload executes when the visitor loads that page; the described behavior does not require additional interaction.

Where does the unsafe system name value appear on the login page?

It is written into the description meta element's content attribute, the title element, and an h4 header. The h4 placement is parsed as markup, allowing injected HTML and event handlers to execute.

What is the impact of a successful stored payload?

The script executes in the origin serving the login form and alongside its credential fields. The malicious value remains active until an administrator changes the system name setting.

CVE-2026-26211: Ekushey Project Manager CRM 5.0 Stored XSS via System Name Field

Affected Software

Event History

Frequently Asked Questions

Who can trigger the stored payload, and who is exposed to it?

Does exploitation require a victim to authenticate or interact with the page?

Where does the unsafe system name value appear on the login page?

What is the impact of a successful stored payload?

Company

Resources

Contact

Frequently Asked Questions

Who can trigger the stored payload, and who is exposed to it?

Does exploitation require a victim to authenticate or interact with the page?

Where does the unsafe system name value appear on the login page?

What is the impact of a successful stored payload?