CVE-2025-14694VulnerabilityPublished 15 Dec 2025Updated 24 Feb 2026

CVE-2025-14694: ketr JEPaaS · SQL Injection

Affects ketr JEPaaSSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.1Medium

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

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

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/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system 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 Vulnerable System.
Vulnerable system 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 to the Vulnerable System.
Vulnerable system 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 Vulnerable System 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 Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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
GitHubc3p0ooo-yiqiyin/JEPaaS`pkg:github/c3p0ooo-yiqiyin/JEPaaS`Other threats	Affected =7.2.0 =7.2.1 =7.2.2 =7.2.3 =7.2.4 =7.2.5 =7.2.6 =7.2.7 =7.2.8	Fixed in–

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

AI-suggested

1. Implement strict input validation and sanitization on the 'keyWord' parameter at the application level to prevent SQL injection attempts. 2. Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection payloads targeting the vulnerable endpoint. 3. Restrict database user privileges associated with the JEPaaS application to the minimum necessary, limiting the potential damage from injection attacks. 4. Monitor logs for unusual database queries or access patterns indicative of exploitation attempts. 5. Isolate the JEPaaS environment within segmented network zones to reduce lateral movement risk. 6. Engage in active threat hunting for signs of compromise related to this vulnerability. 7. Contact the vendor for updates and subscribe to security advisories for forthcoming patches. 8. Consider temporary disabling or restricting access to the readAllPostil function if feasible until a patch is available. 9. Conduct regular security assessments and penetration testing focusing on injection vulnerabilities. 10. Educate privileged users about the risks and enforce strong authentication and access controls to prevent privilege escalation.

Description

A vulnerability was found in ketr JEPaaS up to 7.2.8. This impacts the function readAllPostil of the file /je/postil/postil/readAllPostil. Performing a manipulation of the argument keyWord results in sql injection. The attack can be initiated remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The primary impact of CVE-2025-14694 is the potential compromise of sensitive data stored within the ketr JEPaaS platform's backend database. Successful exploitation could allow attackers to execute arbitrary SQL commands, leading to unauthorized data disclosure, data manipulation, or deletion. This could result in data breaches, loss of data integrity, and disruption of service availability. Organizations relying on JEPaaS for critical business functions may face operational downtime and reputational damage. Since exploitation requires high privileges, insider threats or attackers who have already gained elevated access pose the greatest risk. The public availability of exploit code increases the likelihood of opportunistic attacks, especially in environments where patching is delayed. The vendor's lack of response and absence of patches exacerbate the threat, leaving organizations exposed. Overall, the vulnerability could facilitate lateral movement within networks and serve as a foothold for further attacks.

Summary

CVE-2025-14694 is a SQL injection vulnerability identified in the ketr JEPaaS platform, specifically in versions 7.2.0 through 7.2.8. The vulnerability exists in the readAllPostil function located at /je/postil/postil/readAllPostil, where the 'keyWord' parameter is improperly sanitized, allowing attackers to inject malicious SQL queries. This injection flaw can be exploited remotely without user interaction; however, it requires the attacker to have high-level privileges on the system, limiting the ease of exploitation. The vulnerability can lead to unauthorized data access, modification, or deletion, potentially compromising the confidentiality, integrity, and availability of the backend database. The CVSS 4.0 score of 5.1 reflects a medium severity, factoring in the required privileges and limited scope of impact. The lack of scope change and no need for user interaction reduce the overall risk, but the vulnerability remains significant for affected organizations. The absence of official patches necessitates alternative mitigation strategies to protect systems until a vendor fix is issued.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 23:01 UTC

Technical details

References

Community reviews

Related threats