CVE-2026-0942
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Rede Itaú for WooCommerce — Payment PIX, Credit Card and Debit plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the clearOrderLogs() function in all versions up to, and including, 5.1.5. This makes it possible for unauthenticated attackers to delete the Rede Order Logs metadata from all WooCommerce orders.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Rede Itaú for WooCommerce plugin has a clearOrderLogs() function that lacks proper capability validation, allowing any unauthenticated user to delete Rede Order Logs metadata from all WooCommerce orders via an API endpoint or direct function call.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify plugin is installedCheck the WordPress plugins directory (wp-content/plugins) for a folder named 'rede-itau-for-woocommerce' or similar variationAffected if The plugin folder exists in the WordPress installation
-
Identify installed versionOpen the main plugin file (usually named rede-itau-for-woocommerce.php) and locate the Version header in the plugin comment block, or check the plugin admin page for the version numberAffected if Version is below 5.1.6, or the version cannot be confirmed and the plugin is present
-
Check for vulnerable function exposureSearch plugin source files for 'clearOrderLogs' function definition - examine whether it is declared as public and lacks current_user_can() or similar capability checks before executingAffected if A public clearOrderLogs() function exists without proper capability validation in the code
-
Verify API endpoint accessibilityTest accessing common REST API routes for this plugin (such as /wp-json/rede-itau/v1/clear-logs or similar endpoints) without authentication using a tool like curlAffected if The endpoint responds and allows deletion of order metadata without authentication
-
Confirm order log metadata presenceIn WooCommerce, go to an order and check if custom fields related to 'rede_order_logs' or 'rede_transaction' exist in the order metadataAffected if Rede-related metadata fields are present in orders, indicating the plugin functionality is active
A user is affected if the Rede Itaú for WooCommerce plugin is installed with a version below 5.1.6 and the clearOrderLogs function or its API endpoint is accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the plugin to version 5.1.6 or later which should include proper capability checks on the clearOrderLogs() function. If no update is available, consider disabling the plugin until a patched version is released.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0942 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0942 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data