LiveActive security incident?Get immediate response
CVE Record

CVE-2020-23647: Cross Site Scripting (XSS) vulnerability in BoxBilling 4.19, 4.19.1, 4.20, and 4.21 allows remote attackers...

Cross Site Scripting (XSS) vulnerability in BoxBilling 4.19, 4.19.1, 4.20, and 4.21 allows remote attackers to run arbitrary code via the message field on the submit new ticket form.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-23647 is a cross-site scripting issue in BoxBilling ticket submission. A remote attacker could place malicious content in the new-ticket message field, affecting users who later view it. The business risk is account/session impact and unauthorized actions within the affected web application context, not direct server takeover.

Executive priority

Prioritize remediation for internet-facing BoxBilling support portals because unauthenticated attackers can submit malicious ticket content. This is moderate severity: important for web-app account and data protection, but sources do not indicate active exploitation or availability impact.

Technical view

The CVE describes CWE-79 XSS in BoxBilling 4.19, 4.19.1, 4.20, and 4.21 via the submit-new-ticket message field. CVSS 3.1 is 6.1 with network access, low complexity, no privileges, required user interaction, changed scope, and low confidentiality and integrity impact.

Likely exposure

Exposure is most likely where vulnerable BoxBilling versions are deployed and the support ticket submission form is reachable by external users. The CVE source bundle lists affected version details in the title and description, while structured affected product fields are incomplete.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires a user to interact with or view attacker-controlled ticket content. Treat internet-facing helpdesk portals as higher priority than internal-only deployments.

Researcher notes

Evidence is limited to the CVE record and a GitHub issue reference. The bundle does not provide a named patch version, detailed affected CPEs, or confirmed exploitation. Avoid expanding scope beyond BoxBilling versions named in the title and description.

Mitigation direction

  • Identify any BoxBilling 4.19 through 4.21 deployments.
  • Check BoxBilling project guidance for fixed releases or official remediation.
  • Restrict public ticket submission if immediate remediation is unavailable.
  • Review ticket-handling workflows for safe rendering of submitted messages.

Validation and detection

  • Confirm deployed BoxBilling versions against the affected range.
  • Verify whether the submit-new-ticket form is externally reachable.
  • Review stored ticket messages for suspicious markup or script-like content.
  • Perform safe internal XSS validation without using public exploit payloads.
Prepared
Confidence
medium
Sources
3

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.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
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-2020-23647 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
Medium
CVSS
6.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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.

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2020-23647Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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