CVE-2026-5587
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was identified in wbbeyourself MAC-SQL up to 31a9df5e0d520be4769be57a4b9022e5e34a14f4. This affects the function _execute_sql of the file core/agents.py of the component Refiner Agent. The manipulation leads to sql injection. Remote exploitation of the attack is possible. The exploit is publicly available and might be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSQL injection vulnerability in the Refiner Agent's _execute_sql function in core/agents.py allows remote attackers to inject malicious SQL queries. The vulnerability stems from unsanitized user input being passed directly to SQL execution. Exploit code is publicly available.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the Refiner Agent componentSearch for the file core/agents.py in your environment or check if Refiner Agent is listed as an installed componentAffected if The file core/agents.py exists and the Refiner Agent is deployed in your environment
-
Identify the software versionCheck the version of the software package containing core/agents.py using your package manager or software inventory (e.g., pip show, npm list, or container image tags)Affected if The installed version falls within any vulnerable release range for this component
-
Verify database connectivity is enabledInspect the Refiner Agent configuration files or environment variables to confirm if database connections are configured and activeAffected if Database connectivity is enabled and the _execute_sql function can be invoked
-
Check for exposed input paths to _execute_sqlReview application logs, API endpoints, or input channels that feed into the Refiner Agent's _execute_sql function; look for unsanitized parameter handlingAffected if User-supplied or external input can reach the _execute_sql function without validation
-
Inspect input validation controlsExamine the codebase or configuration for presence of input validation, sanitization, or parameterized query implementations in the Refiner Agent moduleAffected if No input validation or parameterized queries are implemented for SQL operations in the Refiner Agent
Your environment is affected if the Refiner Agent component is deployed, database connectivity is active, and unsanitized input can reach the _execute_sql function without validation controls in place.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement parameterized queries or prepared statements in the _execute_sql function to prevent SQL injection. Sanitize and validate all user inputs before passing them to SQL queries. Update to the latest commit if available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5587 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5587 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data