CVE-2026-25044 | Budibase up to 3.33.3 os command injection
VulDBArchived Apr 03, 2026✓ Full text saved
A vulnerability classified as critical has been found in Budibase up to 3.33.3 . Affected by this vulnerability is an unknown functionality. Performing a manipulation results in os command injection. This vulnerability is cataloged as CVE-2026-25044 . It is possible to initiate the attack remotely. There is no exploit available. It is recommended to upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-355180 · CVE-2026-25044 · GCVE-0-2026-25044
BUDIBASE UP TO 3.33.3 OS COMMAND INJECTION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
8.4 $0-$5k 1.03+
Summaryinfo
A vulnerability classified as critical was found in Budibase up to 3.33.3. Affected by this issue is some unknown functionality. Executing a manipulation can lead to os command injection. This vulnerability is registered as CVE-2026-25044. It is possible to launch the attack remotely. No exploit is available. Upgrading the affected component is advised.
Detailsinfo
A vulnerability has been found in Budibase up to 3.33.3 and classified as critical. This vulnerability affects an unknown function. The manipulation with an unknown input leads to a os command injection vulnerability. The CWE definition for the vulnerability is CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
Budibase is an open-source low-code platform. Prior to version 3.33.4, the bash automation step executes user-provided commands using execSync without proper sanitization or validation. User input is processed through processStringSync which allows template interpolation, potentially allowing arbitrary command execution. This issue has been patched in version 3.33.4.
The advisory is shared for download at github.com. This vulnerability was named CVE-2026-25044 since 01/28/2026. The exploitation appears to be easy. The attack can be initiated remotely. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1202.
Upgrading to version 3.33.4 eliminates this vulnerability.
Productinfo
Name
Budibase
Version
3.33.0
3.33.1
3.33.2
3.33.3
Website
Product: https://github.com/Budibase/budibase/
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3info
VulDB Meta Base Score: 8.8
VulDB Meta Temp Score: 8.4
VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Os command injection
CWE: CWE-78 / CWE-77 / CWE-74
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: Budibase 3.33.4
Timelineinfo
01/28/2026 CVE reserved
04/03/2026 +64 days Advisory disclosed
04/03/2026 +0 days VulDB entry created
04/03/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: github.com
Status: Confirmed
CVE: CVE-2026-25044 (🔒)
GCVE (CVE): GCVE-0-2026-25044
GCVE (VulDB): GCVE-100-355180
Entryinfo
Created: 04/03/2026 18:21
Changes: 04/03/2026 18:21 (65)
Complete: 🔍
Cache ID: 99:90A:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸