Unauthenticated Broken Access Control in Stylish Cost Calculator <= 8.3.9 versions.
Product
wordpress stylish-cost-calculator vulnerabilities
6 published CVES affecting wordpress stylish-cost-calculator, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 0
- High
- 1
- Medium
- 5
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest wordpress stylish-cost-calculator CVEs
Newest publication first
-
HighCVSS 7.5 EPSS 0.39%
-
MediumCVSS 4.3 EPSS 0.11%
Cross-Site request forgery (CSRF) vulnerability in weDevs WooCommerce Conversion Tracking allows Cross Site Request Forgery. This issue affects WooCommerce Conversion Tracking: from n/a through 2.0.10.
-
MediumCVSS 6.5 EPSS 0.16%
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Design Stylish Cost Calculator stylish-cost-calculator allows Stored XSS.This issue affects Stylish Cost Calculator: from n/a through <= 8.2.9.
-
MediumCVSS 6.5 EPSS 0.17%
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Design Stylish Cost Calculator stylish-cost-calculator allows DOM-Based XSS.This issue affects Stylish Cost Calculator: from n/a through <= 8.1.5.
-
MediumCVSS 4.3
The Appsero analytics tool used in several plugins is vulnerable to authorization bypass due to a missing capability check on the uninstall_reason_submission function used for feedback submission in versions up to, and including, 1.2.1. This makes it possible for authenticated at...
-
CVE-2021-24822 Stylish Cost Calculator < 7.04 - Subscriber+ Unauthorised AJAX Calls to Stored XSS
PublishedMediumCVSS 5.4 EPSS 0.32%The Stylish Cost Calculator WordPress plugin before 7.0.4 does not have any authorisation and CSRF checks on some of its AJAX actions (available to authenticated users), which could allow any authenticated users, such as subscriber to call them, and perform Stored Cross-Site Scri...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.