# CVE-2026-76635: baserCMS < 5.3.0 SQL Injection and Code Injection via BcDatabaseService.php

> Authenticated administrators can exploit SQL injection and code injection flaws in baserCMS to execute arbitrary code and read sensitive database information.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-cg65-f2m7-9fqj, GHSA-p3p6-469g-p4j2

## What is CVE-2026-76635?

CVE-2026-76635 is a high-severity SQL injection vulnerability in baserproject basercms, published on 20 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-76635?


## How do I fix CVE-2026-76635?

No fix has been published for CVE-2026-76635 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-76635 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-76635 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-76635 and fix it if it is affected.

What it is: CVE-2026-76635 is a high-severity SQL injection vulnerability in baserproject basercms, published on 20 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-76635 exists.

Affected product: baserproject basercms. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-76635/ (Markdown: https://insights.sbomify.com/CVE-2026-76635/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-76635
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-76635
- OSV: https://osv.dev/vulnerability/CVE-2026-76635

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-76635/
Summaries are generated and may contain mistakes; the official description above is the record.