CVE-2026-24553
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2026-01-23

Last updated on: 2026-04-01

Assigner: Patchstack

Description
Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in Dotstore Fraud Prevention For Woocommerce woo-blocker-lite-prevent-fake-orders-and-blacklist-fraud-customers allows Retrieve Embedded Sensitive Data.This issue affects Fraud Prevention For Woocommerce: from n/a through <= 2.3.2.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-23
Last Modified
2026-04-01
Generated
2026-06-16
AI Q&A
2026-01-23
EPSS Evaluated
2026-06-14
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
dotstore fraud_prevention_for_woocommerce to 2.3.1 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-497 The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability is a Sensitive Data Exposure issue in the WordPress plugin 'Fraud Prevention For Woocommerce' (versions up to 2.3.1). It allows a malicious user with subscriber-level privileges to access sensitive system information that should normally be restricted. This exposure could potentially lead to exploitation of other system weaknesses. The vulnerability is classified under OWASP Top 10 category A3: Sensitive Data Exposure and has a low severity with a CVSS score of 4.3. [1]

Compliance Impact

The provided resources do not specify how this vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.

Impact Analysis

The vulnerability could allow unauthorized users to retrieve sensitive information from the system, which might be used to exploit other weaknesses. However, the overall impact is considered low and exploitation is unlikely. It requires only subscriber-level access to exploit, so if an attacker gains such access, they could potentially access restricted data. [1]

Mitigation Strategies

Since no official fix or patched version is currently available for this vulnerability, immediate mitigation steps include limiting subscriber-level privileges to trusted users only and monitoring access to sensitive data. Additionally, using Patchstack's mitigation services may help reduce risk until a patch is released. [1]

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-24553. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart