CVE-2022-40361
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 · uneditedCross Site Scripting Vulnerability in Elite CRM v1.2.11 allows attacker to execute arbitrary code via the language parameter to the /ngs/login endpoint.
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 confidenceThis is a reflected Cross Site Scripting (XSS) vulnerability in Elite CRM v1.2.11. The language parameter in the /ngs/login endpoint does not properly sanitize user input, allowing attackers to inject malicious JavaScript code that executes in the victim's browser when they access the login page.
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= 1.2.11CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Confirm Elite CMS versionLocate the version identifier in the application. Check the source code, an admin dashboard 'About' page, or a version file typically found in the application root or configuration directory. Compare this version number to 1.2.11.Affected if The installed version is exactly 1.2.11
-
Verify /ngs/login endpoint existsAttempt to access the /ngs/login path on the server (e.g., https://example.com/ngs/login or http://localhost/ngs/login). Check if the endpoint returns a login page response.Affected if The /ngs/login endpoint is accessible and returns a page
-
Test language parameter reflectionSend a request to /ngs/login with a test value in the language parameter (e.g., /ngs/login?language=test123). Examine the response HTML to see if 'test123' appears unencoded in the page output.Affected if The language parameter value is reflected in the response without HTML entity encoding (e.g., appears as literal 'test123' rather than '<test123>')
-
Check for XSS payload executionSend a request with a benign XSS probe in the language parameter (e.g., /ngs/login?language=<script>alert(1)</script>). Inspect the response to see if the <script> tags or other HTML special characters are rendered as-is rather than being encoded.Affected if The response contains unescaped HTML characters or JavaScript tags from the input
You are affected if running Elite CMS version 1.2.11 and the /ngs/login endpoint reflects the language parameter input without proper HTML entity encoding.
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 proper input validation and output encoding on the language parameter. Use context-appropriate encoding (HTML entity encoding) when reflecting user input back into the response.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40361 — 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-2022-40361 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