baserCMS before 5.3.0 contains a SQL injection vulnerability in BcDatabaseService.php that allows authenticated administrators to inject attacker-controlled table names and configuration values directly into SQL statements across sequence update, CSV export, and table management operations. Attackers can chain a backup restore code injection flaw, where PHP code outside class definitions in schema files executes unconditionally upon loading, to plant malicious table names and trigger error-based SQL injection that retrieves database version, schema contents, and arbitrary data from the PostgreSQL backend.
CVE-2026-76635
Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-20. a secondary CVSS source baseline 7.2; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.2
- EG Score
- 7.2(high)
- EG Risk
- 37(Track)EG Risk 37/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity72% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 20, 2026
Last Modified
August 20, 2026
Advisory Details (3)
Auto-updated Aug 20, 2026baserCMS < 5.3.0 SQL Injection and Code Injection via BcDatabaseService.php | Advisories | VulnCheck
https://www.vulncheck.com/advisories/basercms-sql-injection-and-code-injection-via-bcdatabaseservice-phpbaserCMS 5.3.0 リリース
Patch available: baserproject/basercms 5.3.0
https://github.com/baserproject/basercms/releases/tag/5.3.0SQL Injection + Code Execution in baserCMS BcDatabaseService · Advisory · baserproject/basercms · GitHub
https://github.com/baserproject/basercms/security/advisories/GHSA-cg65-f2m7-9fqjVendor Advisories for CVE-2026-76635(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 03:30 UTCEG score recompute
- 2026-08-21 03:30 UTCGHSA enrichment
- 2026-08-20 14:25 UTCEG score recompute
- 2026-08-20 14:07 UTCEG score recompute
- 2026-08-20 14:07 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-76635?
When was CVE-2026-76635 disclosed?
What is the CVSS score of CVE-2026-76635?
How do I remediate CVE-2026-76635?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76635
Is Your Infrastructure Affected by CVE-2026-76635?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.