Skip to main content
VulnerabilityPublished Updated

CVE-2024-23995: Beekeeper Studio · Cross-site Scripting

Source CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Apr 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

To mitigate CVE-2024-23995, organizations should implement the following specific measures: 1) Monitor for and apply official patches or updates from Beekeeper Studio as soon as they become available to address the XSS vulnerability. 2) Until patches are released, restrict the use of untrusted or user-generated input in database column names, especially avoiding importing or displaying data from unknown or unverified sources. 3) Employ input validation and sanitization at the application or database layer to prevent malicious scripts from being stored or rendered in UI components. 4) Educate users about the risks of opening database tables with suspicious or unexpected column names and encourage cautious behavior when interacting with shared databases. 5) Consider deploying web application firewalls (WAFs) or endpoint security solutions capable of detecting and blocking XSS payloads targeting the application interface. 6) Review and harden client-side security settings to limit the impact of script execution, such as enabling Content Security Policy (CSP) headers if applicable. 7) Conduct regular security assessments and code reviews of custom integrations or plugins that interact with Beekeeper Studio to identify and remediate similar injection points.

Description

Cross Site Scripting (XSS) in Beekeeper Studio 4.1.13 and earlier allows remote attackers to execute arbitrary code in the column name of a database table in tabulator-popup-container.

References

Community reviews

Loading reviews…