InstaWP Connect Plugin up to 0.0.9.18 on WordPress Setting events_receiver authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in InstaWP Connect Plugin up to 0.0.9.18 on WordPress. It has been declared as critical. Impacted is the function events_receiver of the component Setting Handler. Executing a manipulation can lead to authorization.
This vulnerability is registered as CVE-2023-3956. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability has been found in InstaWP Connect Plugin up to 0.0.9.18 on WordPress (WordPress Plugin) and classified as critical. This vulnerability affects the function events_receiver of the component Setting Handler. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
The InstaWP Connect plugin for WordPress is vulnerable to unauthorized access of data, modification of data and loss of data due to a missing capability check on the 'events_receiver' function in versions up to, and including, 0.0.9.18. This makes it possible for unauthenticated attackers to add, modify or delete post and taxonomy, install, activate or deactivate plugin, change customizer settings, add or modify or delete user including administrator user.
The weakness was published 07/27/2023. The advisory is available at wordfence.com. This vulnerability was named CVE-2023-3956 since 07/26/2023. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 04/10/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
- 0.0.9.0
- 0.0.9.1
- 0.0.9.2
- 0.0.9.3
- 0.0.9.4
- 0.0.9.5
- 0.0.9.6
- 0.0.9.7
- 0.0.9.8
- 0.0.9.9
- 0.0.9.10
- 0.0.9.11
- 0.0.9.12
- 0.0.9.13
- 0.0.9.14
- 0.0.9.15
- 0.0.9.16
- 0.0.9.17
- 0.0.9.18
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 9.8
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: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
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
07/26/2023 🔍07/27/2023 🔍
07/27/2023 🔍
04/10/2026 🔍
Sources
Advisory: 2942363Status: Not defined
CVE: CVE-2023-3956 (🔍)
GCVE (CVE): GCVE-0-2023-3956
GCVE (VulDB): GCVE-100-235570
Entry
Created: 07/27/2023 09:57Updated: 04/10/2026 10:06
Changes: 07/27/2023 09:57 (49), 08/20/2023 08:45 (1), 04/10/2026 10:06 (16)
Complete: 🔍
Cache ID: 216:B98:103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.