CVE-2025-11438VulnerabilityPublished 8 Oct 2025

CVE-2025-11438: JhumanJ OpnForm · Missing Authorization

Affects JhumanJ OpnFormSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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: Low
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
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 8 Oct 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
JhumanJ OpnForm	Affected =1.9.0 =1.9.1 =1.9.2 =1.9.3	Fixed in–

AI-suggested

To mitigate CVE-2025-11438, European organizations should immediately apply the official patch identified by commit beb153ce52dceb971c1518f98333328c95f1ba20 provided by JhumanJ. In addition to patching, organizations should audit all API endpoints, particularly /custom-domains, to verify that proper authorization checks are enforced consistently. Network segmentation should be employed to restrict access to OpnForm API endpoints to trusted internal networks or VPNs. Implementing Web Application Firewalls (WAFs) with rules to detect and block unauthorized API calls can provide an additional layer of defense. Monitoring and logging API access patterns will help detect anomalous or unauthorized activities early. Organizations should also review user privilege assignments to ensure the principle of least privilege is maintained. Regular vulnerability scanning and penetration testing focused on API security will help identify similar issues proactively. Finally, educating development and operations teams about secure API design and authorization best practices will reduce the risk of future vulnerabilities.

Description

A vulnerability has been found in JhumanJ OpnForm up to 1.9.3. This vulnerability affects unknown code of the file /custom-domains of the component API Endpoint. Such manipulation leads to missing authorization. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The name of the patch is beb153ce52dceb971c1518f98333328c95f1ba20. It is best practice to apply a patch to resolve this issue.

Impact

For European organizations, the missing authorization vulnerability in JhumanJ OpnForm could lead to unauthorized access to sensitive configuration or domain-related data managed via the /custom-domains API endpoint. This may result in data leakage, unauthorized changes to domain configurations, or disruption of services relying on OpnForm's API. Organizations in sectors such as finance, healthcare, and government that utilize OpnForm for form management or digital workflows could face operational disruptions or compliance violations if exploited. The remote exploitability without user interaction increases the risk of automated attacks or integration into broader attack campaigns. While the impact on confidentiality, integrity, and availability is limited, the vulnerability could serve as an entry point for further attacks or data exfiltration. European entities with internet-facing OpnForm instances are particularly vulnerable. The absence of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as proof-of-concept code is publicly available. Failure to patch promptly may expose organizations to targeted attacks or opportunistic scanning by threat actors.

Summary

CVE-2025-11438 is a vulnerability discovered in the JhumanJ OpnForm product, specifically affecting versions 1.9.0 through 1.9.3. The issue resides in the API endpoint located at /custom-domains, where a missing authorization check allows remote attackers to perform unauthorized operations. The vulnerability arises from improper access control mechanisms, permitting attackers with low privileges to bypass authorization requirements and manipulate the endpoint remotely without user interaction. The CVSS 4.0 base score is 5.3 (medium severity), reflecting network attack vector, low attack complexity, no privileges required, no user interaction, and limited impact on confidentiality, integrity, and availability. Although no active exploits have been reported in the wild, the vulnerability has been publicly disclosed along with a patch identified by commit beb153ce52dceb971c1518f98333328c95f1ba20. This patch addresses the missing authorization by enforcing proper access controls on the /custom-domains endpoint. The vulnerability could allow unauthorized data access or modification, potentially impacting business processes relying on OpnForm's API. The lack of authentication requirements and remote exploitability increase the risk profile, especially in environments where OpnForm is exposed to untrusted networks. The vulnerability does not affect the software supply chain directly but could be leveraged for lateral movement or privilege escalation within compromised networks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Oct 2025, 06:47 UTC

Technical details

References

Community reviews

Related threats