LiveActive security incident?Get immediate response
CVE Record

CVE-2023-3829: Bug Finder ICOGenie Support Ticket create cross site scripting

A vulnerability was found in Bug Finder ICOGenie 1.0. It has been declared as problematic. This vulnerability affects unknown code of the file /user/ticket/create of the component Support Ticket Handler. The manipulation of the argument message leads to cross site scripting. The attack can be initiated remotely. VDB-235150 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

MediumCVSS 4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

ICOGenie 1.0 has an authenticated cross-site scripting issue in support ticket creation. A user who can submit a ticket could place script content in the message field, potentially affecting staff or users who view it. Sources do not name a vendor patch or confirm active exploitation.

Executive priority

Treat as a moderate web application risk. It is not reported as actively exploited, but customer or user-facing support portals should be reviewed because XSS can undermine trust and session integrity.

Technical view

CVE-2023-3829 is CWE-79 in Bug Finder ICOGenie 1.0, affecting /user/ticket/create in the Support Ticket Handler. Manipulating the message argument leads to XSS. CVSS v2 is 4.0: network-accessible, low complexity, authenticated, partial integrity impact only.

Likely exposure

Exposure is limited to organizations running Bug Finder ICOGenie 1.0 with the support ticket creation route available to authenticated users. Internet-facing customer portals have higher practical exposure than internal-only deployments.

Exploitation context

The sources say the attack can be initiated remotely and requires authentication. CISA KEV is false in the provided bundle, and no cited source confirms active exploitation. Vendor contact reportedly received no response.

Researcher notes

The public record identifies the vulnerable parameter and route but says the affected code is unknown. No exploit steps, patch version, or vendor advisory are provided in the bundle, so validation should remain controlled and evidence-based.

Mitigation direction

  • Inventory ICOGenie deployments and confirm whether version 1.0 is in use.
  • Check Bug Finder or platform guidance before assuming a patch exists.
  • Restrict ticket creation to trusted authenticated users where operationally possible.
  • Review custom code for encoding and validation of ticket message content.
  • Monitor support tickets for suspicious script-like content.

Validation and detection

  • Confirm whether /user/ticket/create is reachable in production environments.
  • Verify authenticated user roles that can submit support ticket messages.
  • Review application behavior when submitted message content is later displayed.
  • Check logs for unusual ticket message submissions around vulnerable routes.
  • Document patch status, compensating controls, and remaining exposure.
Prepared
Confidence
medium
Sources
4

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

CVE-2023-3829 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
4 (2.0)
Known Exploited
No
Published

Vector: AV:N/AC:L/Au:S/C:N/I:P/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
3Source 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
4CVSS 2.0MediumAV:N/AC:L/Au:S/C:N/I:P/A:N82.9Primary CVE score

Vulnerability scoring details

Base CVSS 2.0 score

4Medium
CVSS 2.0 vector shape for CVE-2023-3829Access VectorAccess ComplexityAuthenticationConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: AV:N/AC:L/Au:S/C:N/I:P/A:N

Access Vector
NetworkAdjacentLocal
Access Complexity
LowMediumHigh
Authentication
NoneSingleMultiple
Confidentiality Impact
CompletePartialNone
Integrity Impact
CompletePartialNone
Availability Impact
CompletePartialNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Bug FinderICOGenie1.0Listed
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.