Woo Billingo Plus Plugin on WordPress AJAX Action Szamlazz.hu cross-site request forgery
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
4.1 | $0-$5k | 0.00 |
A vulnerability, which was classified as problematic, was found in Woo Billingo Plus Plugin, Integration for Billingo & Gravity Forms Plugin and Integration for Szamlazz.hu & Gravity Forms Plugin on WordPress (WordPress Plugin) (the affected version is unknown). Affected is an unknown code of the file Szamlazz.hu of the component AJAX Action Handler. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. CVE summarizes:
The Woo Billingo Plus WordPress plugin before 4.4.5.4, Integration for Billingo & Gravity Forms WordPress plugin before 1.0.4, Integration for Szamlazz.hu & Gravity Forms WordPress plugin before 1.2.7 are lacking CSRF checks in various AJAX actions, which could allow attackers to make logged in Shop Managers and above perform unwanted actions, such as deactivate the plugin's license
The weakness was released 10/11/2022. The advisory is shared for download at wpscan.com. This vulnerability is traded as CVE-2022-3154 since 09/07/2022. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available.
Upgrading eliminates this vulnerability.
Product
Type
Name
- Integration for Billingo & Gravity Forms Plugin
- Integration for Szamlazz.hu & Gravity Forms Plugin
- Woo Billingo Plus Plugin
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
09/07/2022 🔍10/11/2022 🔍
10/11/2022 🔍
10/11/2022 🔍
Sources
Advisory: wpscan.comStatus: Confirmed
CVE: CVE-2022-3154 (🔍)
Entry
Created: 10/11/2022 10:19 AMChanges: 10/11/2022 10:19 AM (40)
Complete: 🔍
Cache ID: 18:3CA:40
No comments yet. Languages: en.
Please log in to comment.