LiveActive security incident?Get immediate response
CVE Record

CVE-2018-14583: xyhai.php?s=/Auth/addUser in XYHCMS 3.5 allows CSRF to add a background administrator account.

xyhai.php?s=/Auth/addUser in XYHCMS 3.5 allows CSRF to add a background administrator account.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

XYHCMS 3.5 has a CSRF flaw that could let an attacker cause a logged-in administrator to create another backend administrator account. That can turn a tricked admin session into unauthorized administrative access. Public sources do not identify a fixed version or active exploitation.

Executive priority

Treat as high priority where XYHCMS 3.5 is still used. Unauthorized administrator creation can compromise the site, but urgency should be scoped to confirmed deployments because public sources do not show active exploitation or a named patch.

Technical view

The CVE describes xyhai.php?s=/Auth/addUser in XYHCMS 3.5 as vulnerable to cross-site request forgery for backend administrator creation. The core issue is missing or ineffective request authenticity protection on a privileged user-management action. Available sources provide limited product and remediation detail.

Likely exposure

Exposure appears limited to organizations running XYHCMS 3.5, especially where the administrative interface is reachable by administrators through normal web browsing. Risk depends on administrator authentication state, browser protections, and whether unknown administrator accounts already exist.

Exploitation context

The source bundle does not show KEV listing or confirmed active exploitation. The issue is publicly disclosed through a GitHub issue and CVE records. CSRF generally requires social engineering or web content interaction by an authenticated administrator, but sources do not provide exploit prevalence.

Researcher notes

Evidence is sparse: the CVE description and GitHub reference identify the affected endpoint and product version, but not CVSS, CWE, exploit telemetry, or fixed releases. Validate against the live application and project guidance before asserting patch status.

Mitigation direction

  • Check XYHCMS project or vendor guidance for a fixed release or official workaround.
  • Restrict XYHCMS administrative access to trusted networks, VPN, or allowlisted administrators.
  • Review and remove unexpected backend administrator accounts.
  • If maintaining the code, enforce CSRF validation on administrator creation actions.
  • Monitor administrative account creation events and investigate unexplained changes.

Validation and detection

  • Confirm whether any internet-facing or internal sites run XYHCMS 3.5.
  • Review the administrator creation endpoint for CSRF token enforcement.
  • Inspect backend administrator lists for unknown or recently added accounts.
  • Check web and application logs for unexpected administrator creation events.
  • Verify administrative access is restricted to intended users and networks.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2018-14583 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.