Security readout for executives and security teams
Plain-English summary
CVE-2021-36605 is a cross-site scripting issue in engineercms 1.03. A nickname value is not escaped on the user list page, so script content can run in another user's browser when that page is viewed. Public metadata does not provide CVSS, a confirmed patch, or detailed affected-version data.
Executive priority
Treat this as a targeted remediation item for any engineercms deployment. It is not supported by public active-exploitation evidence, but stored XSS can expose privileged browser sessions if administrators view affected pages.
Technical view
The source description indicates an output-encoding failure in the nickname field rendered on the user list page. Because the value executes when the page is viewed, this is consistent with stored XSS behavior. The CVE record has unknown severity, no CVSS vector, and sparse affected-product metadata.
Likely exposure
Exposure is most likely in deployments running engineercms 1.03, especially where untrusted or lower-privileged users can set nickname values that administrators or other users later view.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not listed as KEV in the bundle. The impact depends on who can edit nicknames and who can access the user list page.
Researcher notes
Evidence is limited to the CVE description and linked GitHub issue. The affected metadata is incomplete, so validate product/version locally. Avoid assuming broader version impact or a vendor patch unless confirmed by upstream sources.
Mitigation direction
- Check upstream engineercms guidance or issue tracker for a fixed release.
- Restrict access to the user list page until remediation is confirmed.
- If maintaining code, apply output encoding to nickname rendering.
- Review stored nicknames for suspicious script-like content.
- Add regression tests covering nickname rendering safety.
Validation and detection
- Inventory systems running engineercms and identify version 1.03 instances.
- Confirm whether nickname values render unescaped on the user list page.
- Verify which roles can edit nickname fields.
- Verify which roles can view the user list page.
- Check logs and stored profile data for suspicious nickname changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2021-36605 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/3xxx/engineercms/issues/52CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.