Security readout for executives and security teams
Plain-English summary
SkyCaiji 1.2 is reported to let a malicious website cause an authenticated user to add a new administrator account. If the application is in use and an administrator can be tricked while logged in, the business impact could be full administrative compromise.
Executive priority
Prioritize confirmation if SkyCaiji is deployed. The issue can lead to administrator account creation, but urgency depends on actual use, admin exposure, and whether compensating access controls exist.
Technical view
The CVE description and referenced GitHub issue identify a cross-site request forgery issue in SkyCaiji 1.2 allowing creation of an Administrator user. The source bundle provides no CVSS score, CWE, CPE, vendor advisory, fixed version, or confirmed patch details.
Likely exposure
Exposure appears limited to environments running SkyCaiji 1.2. The bundle does not provide CPEs, vendor metadata, affected configuration details, or information about whether later versions are affected.
Exploitation context
No cited source states active exploitation, and the CVE is not listed as KEV in the bundle. The public GitHub issue is evidence of disclosure, not evidence of real-world exploitation.
Researcher notes
Evidence is sparse. Treat the CVE as a CSRF-to-admin-creation report for SkyCaiji 1.2, but do not assume affected CPEs, patch availability, exploit maturity, or version ranges beyond the cited sources.
Mitigation direction
- Check official SkyCaiji project guidance for a fixed release or maintainer recommendation.
- Restrict access to SkyCaiji administrative functions to trusted networks or authenticated management paths.
- Review administrator accounts and remove unknown or unauthorized users.
- Use browser and application controls that reduce CSRF risk where supported.
Validation and detection
- Inventory whether SkyCaiji 1.2 is deployed in any environment.
- Confirm administrative endpoints are not broadly reachable unnecessarily.
- Review user and administrator creation logs for unexpected accounts.
- Check dependency or application records for upgrade status and maintainer guidance.
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-2018-11371 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/zorlan/skycaiji/issues/9CVE 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.