Skip to main content
VulnerabilityPublished Updated

CVE-2026-76635: baserproject basercms · SQL Injection

Affects baserproject basercmsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.6 High : upgrade to 5.3.0 soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.3.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade baserproject basercms to 5.3.0.

Affected software

ProductAffectedFixed in
baserprojectbasercmsAffected
  • <5.3.0
Fixed in–
GitHubbasercmspkg:github/basercmsOther threatsAffected
  • <5.3.0
Fixed in
  • 5.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict administrative access to trusted users only and monitor for suspicious activity related to sequence updates, CSV exports, and table management operations. Avoid using backup restore features that may execute untrusted schema files.

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.

References

Community reviews

Loading reviews…