GiveWP Plugin up to 2.20.2 on WordPress REST API Endpoint /donor-wall information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in GiveWP Plugin up to 2.20.2 on WordPress. The affected element is an unknown function of the file /donor-wall of the component REST API Endpoint. Executing a manipulation can lead to information disclosure. This vulnerability is registered as CVE-2022-2117. No exploit is available.
Details
A vulnerability was found in GiveWP Plugin up to 2.20.2 on WordPress (WordPress Plugin). It has been declared as problematic. This vulnerability affects an unknown functionality of the file /donor-wall of the component REST API Endpoint. The manipulation 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. CVE summarizes:
The GiveWP plugin for WordPress is vulnerable to Sensitive Information Disclosure in versions up to, and including, 2.20.2 via the /donor-wall REST-API endpoint which provides unauthenticated users with donor information even when the donor wall is not enabled. This functionality has been completely removed in version 2.20.2.
The weakness was published 07/19/2022. The advisory is shared for download at wordfence.com. This vulnerability was named CVE-2022-2117 since 06/17/2022. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.
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
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 4.9
VulDB Base Score: 4.3
VulDB Temp Score: 4.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CNA Base Score: 5.3
CNA Vector (Wordfence): 🔍
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
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
06/17/2022 🔍07/19/2022 🔍
07/19/2022 🔍
04/08/2026 🔍
Sources
Advisory: 2743833Status: Not defined
CVE: CVE-2022-2117 (🔍)
GCVE (CVE): GCVE-0-2022-2117
GCVE (VulDB): GCVE-100-204100
Entry
Created: 07/19/2022 07:32Updated: 04/08/2026 23:05
Changes: 07/19/2022 07:32 (40), 08/06/2022 08:11 (1), 08/06/2022 08:13 (12), 04/08/2026 23:05 (26)
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.