JhumanJ OpnForm up to 1.9.3 Forgotten Password /api/password/email information exposure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in JhumanJ OpnForm up to 1.9.3 and classified as problematic. This impacts an unknown function of the file /api/password/email of the component Forgotten Password Handler. Such manipulation leads to information exposure. This vulnerability is referenced as CVE-2025-11443. It is possible to launch the attack remotely. Furthermore, an exploit is available. This issue is currently aligned with Laravel issue #46465, which is why no mitigation action was taken.
Details
A vulnerability was found in JhumanJ OpnForm up to 1.9.3 and classified as problematic. Affected by this issue is an unknown code of the file /api/password/email of the component Forgotten Password Handler. The manipulation with an unknown input leads to a information exposure vulnerability. Using CWE to declare the problem leads to CWE-203. The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not. Impacted is confidentiality.
The advisory is shared for download at docs.google.com. This vulnerability is handled as CVE-2025-11443. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1592.
The exploit is available at docs.google.com. It is declared as proof-of-concept. This issue is currently aligned with Laravel issue #46465, which is why no mitigation action was taken.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.6
VulDB Base Score: 3.7
VulDB Temp Score: 3.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.7
CNA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Information exposureCWE: CWE-203 / CWE-200 / CWE-284
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/07/2025 Advisory disclosed10/07/2025 VulDB entry created
10/08/2025 VulDB entry last update
Sources
Advisory: docs.google.comStatus: Confirmed
CVE: CVE-2025-11443 (🔒)
GCVE (CVE): GCVE-0-2025-11443
GCVE (VulDB): GCVE-100-327380
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 10/07/2025 15:22Updated: 10/08/2025 10:54
Changes: 10/07/2025 15:22 (56), 10/08/2025 10:54 (30)
Complete: 🔍
Submitter: balejin
Cache ID: 216::103
Submit
Accepted
- Submit #666890: GitHub OpnForm 1.9.3 Account Enumeration on Password Recovery (by balejin)
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.