LiveActive security incident?Get immediate response
CVE Record

CVE-2018-10364: BigTree before 4.2.22 has XSS in the Users management page via the name or company field.

BigTree before 4.2.22 has XSS in the Users management page via the name or company field.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

BigTree CMS before 4.2.22 could display unsafe user name or company values on the Users management page. If a privileged CMS user viewed malicious stored content, browser-side script could run in that user’s session. The sources do not show active exploitation.

Executive priority

Treat this as a targeted CMS hardening item, not an emergency internet-wide crisis based on current evidence. Prioritize upgrading any older BigTree administrative deployments because XSS in admin workflows can enable account misuse and content tampering.

Technical view

CVE-2018-10364 is an XSS issue in BigTree CMS before 4.2.22 affecting the Users management page. The cited description names the name and company fields as the input vectors. Public bundle evidence does not include CVSS, CWE, detailed preconditions, or exploit telemetry.

Likely exposure

Exposure is most likely for organizations running BigTree CMS versions earlier than 4.2.22, especially where untrusted or semi-trusted users can influence profile name or company values. The source bundle does not define vendor CPEs, deployment prevalence, or authentication requirements.

Exploitation context

The CVE is not marked as CISA KEV, and the provided sources do not claim active exploitation. Business impact would center on administrative browser compromise, session misuse, or unauthorized CMS actions if malicious content is viewed in the Users management page.

Researcher notes

Evidence is limited to the CVE description, GitHub issue, fix commit, and changelog reference. No CVSS, CWE mapping, exploit-in-the-wild report, or precise privilege model is present in the provided bundle. Validate assumptions against the deployed BigTree version and local user-management workflow.

Mitigation direction

  • Upgrade BigTree CMS to 4.2.22 or later using vendor release guidance.
  • Restrict CMS administrative access to trusted users and networks until upgraded.
  • Review user profile data for unexpected script-like content in name or company fields.
  • Monitor CMS administrator sessions and logs for unusual activity.

Validation and detection

  • Inventory BigTree CMS installations and confirm running version numbers.
  • Check whether any installation is earlier than 4.2.22.
  • Review the Users management page handling for name and company output encoding.
  • Confirm the vendor commit or equivalent fix is present in deployed code.
Prepared
Confidence
medium
Sources
5

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-10364 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
4Source links

CVSS and timeline data

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

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.