Skip to main content
VulnerabilityPublished Updated

CVE-2026-5587: wbbeyourself MAC-SQL · SQL Injection

Affects wbbeyourself MAC-SQLSource CVE Database V5

0
Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
wbbeyourselfMAC-SQLAffected
  • =31a9df5e0d520be4769be57a4b9022e5e34a14f4
Fixed in–

AI-suggested

Until a patch is released, consider restricting network access to the vulnerable component and applying any available input validation or query parameterization as a temporary mitigation.

Description

CVE-2026-5587 is a medium-severity SQL injection vulnerability in the wbbeyourself MAC-SQL product affecting the _execute_sql function in core/agents.py within the Refiner Agent component. The vulnerability allows remote attackers to manipulate SQL queries, potentially leading to unauthorized database access or modification. Exploits are publicly available, increasing the risk of exploitation. The product uses a rolling release model, and no specific patched versions or official remediation guidance have been provided. The vendor was contacted but did not respond, and no patch or mitigation details are currently confirmed.

References

Community reviews

Loading reviews…