# CVE-2026-40529: SQL injection in CMS ALAYA

> An attacker with administrative interface access can perform SQL injection to read or modify database information in CMS ALAYA.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/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:** 23 Apr 2026
- **Updated:** 23 Apr 2026
- **Also known as:** GHSA-g347-f6xx-g55w

## What is CVE-2026-40529?

CVE-2026-40529 is a medium-severity SQL injection vulnerability in KANATA Limited CMS ALAYA, published on 23 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

CMS ALAYA provided by KANATA Limited contains an SQL injection vulnerability. Information stored in the database may be obtained or altered by an attacker with access to the administrative interface.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2026-40529 being exploited?

There is no known exploitation of CVE-2026-40529 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40529 is a medium-severity SQL injection vulnerability in KANATA Limited CMS ALAYA, published on 23 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-40529 in the wild and no public exploit code.

Affected product: KANATA Limited CMS ALAYA. 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-40529/ (Markdown: https://insights.sbomify.com/CVE-2026-40529/index.md)
```

## Sources

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

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