LiveActive security incident?Get immediate response
CVE Record

CVE-2023-36816: Cross-Site Scripting (XSS) at Account creation in 2FAuth

2FA is a Web app to manage Two-Factor Authentication (2FA) accounts and generate their security codes. Cross site scripting (XSS) injection can be done via the account/service field. This was tested in docker-compose environment. This vulnerability has been patched in version 4.0.3.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

2FAuth before 4.0.3 allows cross-site scripting through the account/service field during account creation. A malicious value could run script in a user’s browser when viewed, affecting confidentiality and availability according to the CVSS data. Organizations running self-hosted 2FAuth should upgrade, but there is no cited evidence of active exploitation.

Executive priority

Handle in the normal vulnerability remediation cycle, faster for shared or internet-accessible 2FAuth deployments. The issue is patched and medium severity, but it affects a security-sensitive application that stores 2FA account data.

Technical view

CVE-2023-36816 is CWE-79 XSS in Bubka 2FAuth versions before 4.0.3. The source identifies the account/service field as the injection point and states testing used a docker-compose environment. The CVSS 3.1 score is 6.1 with local attack vector, low complexity, no privileges, and required user interaction.

Likely exposure

Exposure is limited to organizations running Bubka 2FAuth versions older than 4.0.3. Risk is higher where untrusted or low-trust users can create or import account entries that others may later view.

Exploitation context

The provided sources do not show public exploitation or CISA KEV listing. Exploitation requires a user interaction condition in the CVSS vector. Treat this as a credible stored-input XSS issue, not as confirmed active exploitation.

Researcher notes

Evidence is narrow but clear: affected product, field, CWE, CVSS, and fixed version are identified. The sources do not describe broader affected components, bypass details, exploit availability, or compensating controls beyond upgrading to 4.0.3.

Mitigation direction

  • Upgrade Bubka 2FAuth to version 4.0.3 or later.
  • Review the GitHub advisory and 4.0.3 release notes before rollout.
  • Limit account creation or import to trusted users until upgraded.
  • Review existing account/service values for suspicious script-like content.
  • Back up data before remediation or cleanup changes.

Validation and detection

  • Inventory all 2FAuth deployments and record running versions.
  • Confirm no instance is running a version earlier than 4.0.3.
  • Review account creation workflows using a non-production test instance.
  • Check account/service field data for unexpected active content markers.
  • Document upgrade status and any cleanup performed.
Prepared
Confidence
high
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
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. 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-36816 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:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H

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
6.1CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H1.84.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Bubka2FAuth< 4.0.3Listed
Weakness

CWE details

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