JhumanJ OpnForm API Endpoint cross-site request forgery
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| JhumanJ | OpnForm | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Jhumanj | Opnform | — |
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.285% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:jhumanj:opnform:*:*:*:*:*:*:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Jhumanj
Jhumanj opnform |
|
| Vendors & Products |
Jhumanj
Jhumanj opnform |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A security flaw has been discovered in JhumanJ OpnForm up to 1.9.3. The impacted element is an unknown function of the component API Endpoint. The manipulation results in cross-site request forgery. The attack may be performed from remote. The exploit has been released to the public and may be exploited. The vendor has stated that API calls require authentication through Authorization Bearer Tokens, so classic CSRF attacks do not apply here. An attacker would need to possess the JWT through means such as XSS which were mitigated, disabling any form of initial access. | |
| Title | JhumanJ OpnForm API Endpoint cross-site request forgery | |
| Weaknesses | CWE-352 CWE-862 |
|
| References |
| |
| Metrics |
cvssV2_0
|