CVE-2026-30995
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSlah CMS v1.5.0 and below was discovered to contain a SQL injection vulnerability via the id parameter in the vereador_ver.php endpoint.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSQL injection vulnerability in Slah CMS v1.5.0 and below allows attackers to inject malicious SQL queries via the id parameter in the vereador_ver.php endpoint, potentially enabling unauthorized data access, modification, or database compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Slah CMS installation and versionCheck your web root for the presence of Slah CMS by looking for characteristic files such as index.php, admin/, or config files. Check the version by inspecting a README, VERSION file, or the header of a main PHP file that typically contains a version constant.Affected if The installed version is Slah CMS v1.5.0 or any version below 1.5.0.
-
Locate the vereador_ver.php fileSearch your web document root for the file named vereacdor_ver.php. This file is typically found in a public-facing directory related to councilor/vereador content.Affected if The file exists in your Slah CMS installation.
-
Inspect SQL query handling in vereador_ver.phpOpen vereacdor_ver.php in a text editor and search for SQL queries (SELECT, INSERT, UPDATE, DELETE statements). Look for occurrences of the 'id' parameter being directly concatenated into SQL strings without using prepared statements or parameter binding.Affected if The file contains SQL queries that use the 'id' parameter directly in string concatenation or interpolation without parameterized queries.
-
Verify dynamic SQL execution without prepared statementsReview the PHP code around the 'id' parameter usage. Check if functions like mysqli_query(), PDO::query(), or similar are called with the 'id' parameter embedded directly in the SQL string, rather than being passed as a bound parameter.Affected if The 'id' parameter is passed directly to SQL execution functions without being bound as a prepared statement parameter.
Your environment is affected if you are running Slah CMS version 1.5.0 or below AND the vereador_ver.php file exists AND the 'id' parameter is used in dynamic SQL queries without prepared statement parameterization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace dynamic SQL queries with parameterized queries/prepared statements in vereador_ver.php and conduct a security audit of all other PHP files for similar SQL injection patterns.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30995 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-30995 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data