VulnerabilityPublished 23 Apr 2026

CVE-2026-40529: KANATA CMS ALAYA · SQL Injection

Affects KANATA CMS ALAYASource CVE Database V5

Compare

Not known to be exploited · CVSS 4.7 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.0 base score

4.7Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
KANATA LimitedCMS ALAYA	Affected =7.4.1.4 and earlier	Fixed in–

AI-suggested

Until an official fix is released, restrict administrative interface access to trusted users only and monitor for suspicious activity related to database queries. Avoid exposing the administrative interface to untrusted networks.

Description

KANATA Limited's CMS ALAYA version 7.4.1.4 and earlier contains an SQL injection vulnerability that allows an attacker with administrative interface access to obtain or alter information stored in the database. The vulnerability is classified as medium severity with a CVSS score of 4.7. There is no confirmed patch or official remediation available at this time. Exploits in the wild are not known. Users should verify vendor advisories for updates and consider restricting administrative access to trusted personnel until a fix is available.

Impact

An attacker with access to the administrative interface can exploit this SQL injection vulnerability to obtain or alter data stored in the CMS ALAYA database. This could lead to unauthorized disclosure, modification, or disruption of data. However, exploitation requires administrative privileges, limiting the scope of impact. There are no known exploits in the wild.

Summary

CVE-2026-40529 is an SQL injection vulnerability in KANATA Limited's CMS ALAYA affecting versions 7.4.1.4 and earlier. The vulnerability arises from improper neutralization of special elements used in SQL commands, enabling attackers with administrative interface access to read or modify database information. The CVSS 3.0 base score is 4.7, reflecting network attack vector, low attack complexity, high privileges required, no user interaction, and impacts on confidentiality, integrity, and availability at a low level.

References

jvn.jp/en/jp/JVN08026319/ (opens in a new tab)

Community reviews

Loading reviews…