meum WP Crowdfunding Plugin up to 2.2.0 on WordPress resource injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.78- |
Summary
A vulnerability classified as problematic has been found in meum WP Crowdfunding Plugin up to 2.2.0. This vulnerability affects unknown code. The manipulation leads to resource injection. This vulnerability is documented as CVE-2026-73189. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability, which was classified as problematic, has been found in meum WP Crowdfunding Plugin up to 2.2.0. This issue affects some unknown processing. The manipulation with an unknown input leads to a resource injection vulnerability. Using CWE to declare the problem leads to CWE-99. The product receives input from an upstream component, but it does not restrict or incorrectly restricts the input before it is used as an identifier for a resource that may be outside the intended sphere of control. Impacted is confidentiality. The summary by CVE is:
Subscriber Insecure Direct Object References (IDOR) in WP Crowdfunding < 2.2.1 versions.
It is possible to read the advisory at patchstack.com. The identification of this vulnerability is CVE-2026-73189 since 08/11/2026. The exploitation is known to be easy. The attack may be initiated remotely. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 2.2.1 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (Patchstack): 🔒
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: Resource injectionCWE: CWE-99
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
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: WP Crowdfunding Plugin 2.2.1
Timeline
08/11/2026 CVE reserved08/18/2026 Advisory disclosed
08/18/2026 VulDB entry created
08/18/2026 VulDB entry last update
Sources
Advisory: patchstack.comStatus: Confirmed
CVE: CVE-2026-73189 (🔒)
GCVE (CVE): GCVE-0-2026-73189
GCVE (VulDB): GCVE-100-391691
Entry
Created: 08/18/2026 16:48Changes: 08/18/2026 16:48 (64)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.