PatchSiren cyber security CVE debrief
CVE-2026-113405 YS-infoware CVE debrief
A SQL Injection vulnerability exists in BA-Workflow developed by YS-infoware. Authenticated remote attackers can inject arbitrary SQL statements to read, modify, and delete database contents. This vulnerability has a CVSS score of 8.7 and is classified as HIGH severity. The vulnerability allows attackers to manipulate database content, potentially leading to data breaches and system compromise. Defenders should verify exposure and assess potential impact on database integrity. The CVE record and NVD vulnerability detail page provide information on the vulnerability, but details on affected versions, exploitation, and remediation are limited.
- Vendor
- YS-infoware
- Product
- BA-Workflow
- CVSS
- HIGH 8.7
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-20
- Original CVE updated
- 2026-10-20
- Advisory published
- 2026-10-20
- Advisory updated
- 2026-10-20
Who should care
Defenders responsible for BA-Workflow systems, database administrators, and security teams should assess exposure and potential impact. They should prioritize verifying exposure, evaluating potential database content manipulation, and implementing compensating controls to restrict database access. Security teams must consider the high severity of this SQL Injection vulnerability and its potential operational impacts.
Why it matters
Defenders should prioritize verifying exposure and assessing potential impact on database integrity due to the high severity SQL Injection vulnerability in BA-Workflow developed by YS-infoware.
- Potential database content manipulation
- Possible data breaches due to unauthorized access
- Risk of system compromise through SQL injection
Technical summary
The BA-Workflow developed by YS-infoware has a SQL Injection vulnerability. Authenticated remote attackers can inject arbitrary SQL statements to read, modify, and delete database contents. The CVSS score for this vulnerability is 8.7, indicating high severity.
Defensive priority
Defenders should prioritize verifying exposure and assessing potential impact on database integrity.
Recommended defensive actions
- Verify exposure by checking system configurations and inventory
- Assess potential impact on database integrity
- Implement compensating controls to restrict database access
Evidence notes
The CVE record and NVD vulnerability detail page provide information on the vulnerability, but details on affected versions, exploitation, and remediation are limited.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-113405 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-113405
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-113405 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-113405
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://www.twcert.org.tw/en/cp-139-11299-0cbfd-2.html
-
Source reference
Unverified legacy reference
URL: https://www.twcert.org.tw/tw/cp-132-11298-d9dd5-1.html
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.