AccessAlly Plugin up to 3.5.6 on WordPress product-shortcode.php accessally_order_form information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in AccessAlly Plugin up to 3.5.6 on WordPress and classified as problematic. Affected by this vulnerability is an unknown functionality of the file resource/frontend/product/product-shortcode.php. This manipulation of the argument accessally_order_form causes information disclosure. This vulnerability is tracked as CVE-2021-24226. The attack is possible to be carried out remotely. No exploit exists. The affected component should be upgraded.
Details
A vulnerability has been found in AccessAlly Plugin up to 3.5.6 on WordPress (WordPress Plugin) and classified as problematic. Affected by this vulnerability is an unknown part of the file resource/frontend/product/product-shortcode.php. The manipulation of the argument accessally_order_form with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality.
The weakness was disclosed 04/12/2021. The advisory is shared at wpscan.com. This vulnerability is known as CVE-2021-24226. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
By approaching the search of inurl:resource/frontend/product/product-shortcode.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 3.5.7 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: AccessAlly Plugin 3.5.7
Timeline
01/14/2021 🔍04/12/2021 🔍
04/12/2021 🔍
04/16/2021 🔍
Sources
Advisory: wpscan.comStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2021-24226 (🔍)
GCVE (CVE): GCVE-0-2021-24226
GCVE (VulDB): GCVE-100-172777
Entry
Created: 04/12/2021 19:52Updated: 04/16/2021 07:36
Changes: 04/12/2021 19:52 (40), 04/16/2021 07:36 (6)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.