Security readout for executives and security teams
Plain-English summary
WTCMS 1.0 is reported to allow cross-site request forgery that can create an administrator account. In business terms, an authenticated administrator could be tricked into causing a new privileged account to be added, creating a path to site takeover.
Executive priority
Treat as high priority if WTCMS 1.0 is in use, because the reported outcome is administrator account creation. If WTCMS is absent, no action is needed beyond recording the assessment.
Technical view
CVE-2018-10267 describes CSRF in WTCMS 1.0 affecting the administrator user-add action. The source bundle provides no CVSS score, CWE, CPE, patch version, or confirmed affected versions beyond WTCMS 1.0.
Likely exposure
Exposure appears limited to organizations running WTCMS 1.0. The sources do not identify CPEs, hosted deployments, forks, or later affected versions, so asset validation is necessary.
Exploitation context
The source bundle does not show KEV listing or confirmed active exploitation. The described risk is CSRF against an authenticated administrative workflow, with potential creation of an unwanted administrator account.
Researcher notes
Evidence is sparse: the CVE description and references identify CSRF to add an administrator account, but provide no standardized scoring, affected CPEs, remediation version, or exploitation confirmation in the supplied bundle.
Mitigation direction
- Identify any WTCMS 1.0 deployments and prioritize them for review.
- Check the project issue and vendor guidance for patch or upgrade status.
- Restrict access to administrative interfaces where operationally possible.
- Review administrative accounts and remove any unauthorized users.
- Consider retiring or replacing unsupported WTCMS 1.0 installations.
Validation and detection
- Confirm whether WTCMS 1.0 is present in production or internal environments.
- Review admin user creation history for unexpected accounts.
- Check whether administrative actions enforce anti-CSRF protection.
- Verify administrative interfaces are not broadly reachable.
- Document any compensating controls until vendor guidance is confirmed.
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-10267 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/taosir/wtcms/issues/1CVE reference · x_refsource_MISC
- https://www.hackpwn.me/2018/04/21/1/CVE 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.