CVE-2025-40990
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedStored Cross Site Scripting vulnerability in Ekushey CRM v5.0 by Creativeitem, due to lack of proper validation of user inputs via the "/ekushey/index.php/client/project_bug/create/xxx", affecting to "title" and "description" parameters via POST. This vulnerability could allow a remote attacker to send a specially crafted query to an authenticated user and steal his/her cookie session details.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStored Cross Site Scripting (XSS) vulnerability in Ekushey CRM v5.0 in the project bug creation form at /ekushey/index.php/client/project_bug/create/xxx. The 'title' and 'description' POST parameters lack proper input validation, allowing injection of malicious JavaScript that persists and executes when authenticated users view the submitted bug reports, enabling cookie/session theft.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 5.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Ekushey CRM installationLook for the /ekushey/ directory or check web server document roots for this application. Inspect page footers or admin panels for 'Ekushey CRM' branding which typically displays the version number.Affected if The application is installed and displays version 5.0 specifically
-
Check if project bug module is enabledNavigate to or enumerate the URL path /ekushey/index.php/client/project_bug/ - attempt to access the create endpoint pattern /ekushey/index.php/client/project_bug/create/ followed by any project ID.Affected if The bug creation module is accessible to authenticated users
-
Verify authenticated user access to bug creationLog in as an authenticated user (client-level account) and attempt to access the bug creation form. Check if POST parameters 'title' and 'description' are accepted by the form.Affected if Authenticated users can access the bug creation form and submit POST requests to it
-
Inspect stored bug reports for XSS executionAfter submitting a bug report with a test payload (e.g., <script>alert('XSS')</script>) in the title or description fields, view the submitted bug report as a different authenticated user. Check if the script executes in the browser.Affected if The submitted payload persists and executes when other users view the bug report, indicating the XSS is stored and exploitable
A user is affected if they run Ekushey CRM version 5.0 and have the project bug creation module accessible to authenticated users, since the lack of input validation on title and description fields allows stored XSS to persist.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation with whitelist approach and context-aware output encoding for all user-supplied data in the bug creation form; add Content Security Policy (CSP) headers as defense-in-depth.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40990 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-40990 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data