LiveActive security incident?Get immediate response
CVE Record

CVE-2023-36222: Cross Site Scripting vulnerability in mlogclub bbs-go v.

Cross Site Scripting vulnerability in mlogclub bbs-go v. 3.5.5. and before allows a remote attacker to execute arbitrary code via a crafted payload to the comment parameter in the article function.

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

Security readout for executives and security teams

Plain-English summary

CVE-2023-36222 describes a cross-site scripting issue in mlogclub bbs-go 3.5.5 and earlier. A remote attacker may be able to submit a malicious article comment that executes script in another user's browser. Business impact depends on whether the forum is internet-facing and trusted users view attacker-controlled comments.

Executive priority

Treat as a targeted web application risk, not a confirmed emergency. Prioritize quickly if bbs-go is public-facing, supports authenticated users, or is used for customer/community engagement.

Technical view

The reported flaw is XSS through the comment parameter in the article function. The source bundle does not provide CVSS, CWE, patch status, or detailed affected CPEs. Treat the affected scope as bbs-go 3.5.5 and earlier based on the CVE description, and verify against upstream guidance.

Likely exposure

Organizations are likely exposed only if they run mlogclub bbs-go, especially public forums accepting article comments. Exposure is highest for versions 3.5.5 and earlier, but the bundle lacks authoritative package metadata or fixed-version information.

Exploitation context

The bundle does not cite active exploitation, and KEV is false. The issue is remotely reachable where article comments are enabled, but no exploit maturity, public weaponization, or real-world campaign evidence is provided.

Researcher notes

Evidence is thin: no CVSS vector, CWE, fixed version, or vendor advisory is included. The CVE wording says arbitrary code, but the described class is XSS, so browser-side script execution is the defensible interpretation.

Mitigation direction

  • Review upstream repository and issue 206 for vendor-confirmed fixes or safe upgrade guidance.
  • Prioritize exposed bbs-go instances running version 3.5.5 or earlier.
  • Restrict or moderate article comments until maintained, fixed code is confirmed.
  • Ensure comment content is encoded or sanitized before rendering.
  • Monitor for unusual comment submissions and XSS-related user reports.

Validation and detection

  • Inventory any mlogclub bbs-go deployments and record running versions.
  • Confirm whether article comments are enabled on public or semi-public pages.
  • Review comment rendering paths for output encoding and sanitization.
  • Check upstream issue 206 and repository history for fix references.
  • Search logs for suspicious comment submissions without replaying payloads.
Prepared
Confidence
medium
Sources
4

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-36222 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
3Timeline events
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

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.