AnyComment Plugin prior 0.2.18 on WordPress Rating race condition
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in AnyComment Plugin on WordPress. Impacted is an unknown function of the component Rating Handler. The manipulation results in race condition. This vulnerability is reported as CVE-2022-0279. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in AnyComment Plugin on WordPress (WordPress Plugin). Affected is an unknown functionality of the component Rating Handler. The manipulation with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was disclosed 02/21/2022. The advisory is shared for download at wpscan.com. This vulnerability is traded as CVE-2022-0279 since 01/19/2022. There are neither technical details nor an exploit publicly available.
Upgrading to version 0.2.18 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.6VulDB Meta Temp Score: 4.4
VulDB Base Score: 4.6
VulDB Temp Score: 4.4
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: Race conditionCWE: CWE-362
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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: 🔍
Upgrade: AnyComment Plugin 0.2.18
Timeline
01/19/2022 🔍02/21/2022 🔍
02/21/2022 🔍
02/25/2022 🔍
Sources
Advisory: wpscan.comStatus: Confirmed
CVE: CVE-2022-0279 (🔍)
GCVE (CVE): GCVE-0-2022-0279
GCVE (VulDB): GCVE-100-193572
Entry
Created: 02/21/2022 14:43Updated: 02/25/2022 09:32
Changes: 02/21/2022 14:43 (38), 02/25/2022 09:32 (1)
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.