Benjamin Balet Jorani 1.0 Leaves.php Comment cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Benjamin Balet Jorani 1.0. It has been declared as problematic. Affected by this issue is some unknown functionality of the file application/controllers/Leaves.php. Executing a manipulation of the argument Comment can lead to cross site scripting. This vulnerability is tracked as CVE-2022-34133. The attack can be launched remotely. No exploit exists. It is advisable to implement a patch to correct this issue.
Details
A vulnerability classified as problematic was found in Benjamin Balet Jorani 1.0. This vulnerability affects some unknown processing of the file application/controllers/Leaves.php. The manipulation of the argument Comment with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity. CVE summarizes:
Jorani v1.0 was discovered to contain a cross-site scripting (XSS) vulnerability via the Comment parameter at application/controllers/Leaves.php.
The weakness was disclosed 06/28/2022 as 369. The advisory is shared for download at github.com. This vulnerability was named CVE-2022-34133 since 06/20/2022. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1059.007.
By approaching the search of inurl:application/controllers/Leaves.php it is possible to find vulnerable targets with Google Hacking.
Applying the patch 3d01cef4ee9cdd70cfe1ac4fd7f5d607dda0d0ca is able to eliminate this problem. The bugfix is ready for download at github.com.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.7
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
NVD 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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 3d01cef4ee9cdd70cfe1ac4fd7f5d607dda0d0ca
Timeline
06/20/2022 🔍06/28/2022 🔍
06/28/2022 🔍
03/30/2026 🔍
Sources
Advisory: 369Status: Confirmed
CVE: CVE-2022-34133 (🔍)
GCVE (CVE): GCVE-0-2022-34133
GCVE (VulDB): GCVE-100-202852
Entry
Created: 06/28/2022 07:52Updated: 03/30/2026 20:28
Changes: 06/28/2022 07:52 (24), 06/28/2022 07:53 (19), 07/16/2022 08:02 (18), 03/30/2026 20:28 (16)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.