CVE-2026-12076
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 · uneditedRaytha CMS is vulnerable to SQL Injection within the OData filter parsing pipeline. The vulnerability allows a remote, unauthenticated attacker to execute arbitrary SQL statements against the underlying PostgreSQL database, leading to full database compromise, including credential extraction. Because vendor contact attempts were unsuccessful, the vulnerability has only been confirmed in version 1.5.2 but may also affect other versions.
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 · high confidenceRaytha CMS 1.5.2 contains a SQL Injection vulnerability in its OData filter parsing pipeline. A remote, unauthenticated attacker can inject arbitrary SQL statements through the OData filter parameters, enabling full database compromise including extraction of stored credentials from the PostgreSQL database.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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.
-
Identify installed Raytha CMS versionCheck the application's version by examining the deployed files, typically found in a version.json, about page, or the application's startup/configuration files. You may also query the runtime environment or admin dashboard if accessible.Affected if The installed version is 1.5.2, or if the version cannot be determined but the application is known to be Raytha CMS.
-
Locate OData API endpointsReview the application's routing configuration or web server logs to identify exposed OData endpoints. Common patterns include /api/odata/, /odata/, or similar paths under the API base URL.Affected if OData endpoints are accessible without authentication and accept filter query parameters.
-
Verify OData filter parameter processing is activeInspect the application's configuration files (such as appsettings.json, web.config, or environment variables) to confirm that OData services are registered and the filter parsing pipeline is enabled.Affected if OData filtering is enabled and the feature processes user-supplied filter parameters without sanitization.
-
Check PostgreSQL database connectionExamine the application's database configuration to confirm it uses PostgreSQL as the backend, since the vulnerability impact specifically references PostgreSQL credential extraction.Affected if The application connects to a PostgreSQL database that stores user credentials.
A user is affected if running Raytha CMS version 1.5.2 with OData API endpoints exposed and the filter parsing pipeline enabled, connected to a PostgreSQL database.
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 dataSince no vendor patch is available, immediately restrict or disable the OData API endpoints if possible, or implement web application firewall (WAF) rules to detect and block SQL injection patterns in query parameters until a code-level fix using parameterized queries can be applied.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12076 — 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-12076 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