CVE-2026-27697
SQL Injection in baserCMS Blog Posts Allows Data Exposure
Publication date: 2026-03-31
Last updated on: 2026-04-01
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| basercms | basercms | to 5.2.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-27697 is a SQL injection vulnerability in baserCMS affecting blog posts in versions 5.2.2 and earlier.
This vulnerability allows attackers to remotely execute malicious SQL commands without needing any privileges or user interaction.
It is classified as moderate severity with a CVSS v4 base score of 6.9.
How can this vulnerability impact me? :
An attacker exploiting this vulnerability can cause limited unauthorized data disclosure, modification, or service disruption on the affected baserCMS system.
The impact on confidentiality, integrity, and availability is considered low.
No further system impacts beyond these have been reported.
What immediate steps should I take to mitigate this vulnerability?
To mitigate the SQL injection vulnerability in baserCMS blog posts, you should update baserCMS to version 5.2.3 or later, where the issue has been patched.
This update removes the vulnerability that allows remote attackers to execute malicious SQL commands without any privileges or user interaction.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify any direct impact of this SQL injection vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.