Missing AuthorizationWeakness · CWE-862

CVE-2024-1119

MEDIUM · 5.3 CVSS v3.1 Published 2024-03-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The Order Tip for WooCommerce plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the export_tips_to_csv() function in all versions up to, and including, 1.3.1. This makes it possible for unauthenticated attackers to export the plugin's order fees.

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 confidence

The Order Tip for WooCommerce plugin has a broken access control vulnerability in the export_tips_to_csv() function which lacks a capability check. This allows any unauthenticated user to directly invoke the function and export all order tip/fee data from the WooCommerce store, exposing sensitive transaction information.

MitigationUpdate the plugin to version 1.3.2 or later which includes the missing capability check. If an update is unavailable, consider disabling the plugin or implementing web application firewall rules to block unauthorized access to the export endpoint.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the plugin is installed
    Navigate to WordPress admin > Plugins and locate 'Order Tip for WooCommerce' in the list of installed plugins. Note whether it is active or inactive.
    Affected if The plugin is installed and active in WordPress.
  2. Identify the installed version
    In the Plugins list, click on the plugin name to view details, or inspect the plugin header in the main PHP file (typically in wp-content/plugins/order-tip-for-woocommerce/). Look for the version string in the plugin metadata.
    Affected if The installed version is lower than 1.3.2, or the version cannot be determined (indicating an older or unmaintained release).
  3. Locate the vulnerable function
    Access the plugin directory via file manager or FTP. Open the main plugin file and search for 'export_tips_to_csv' to confirm the function exists in the installed version.
    Affected if The function export_tips_to_csv() is present in the plugin code.
  4. Check for capability enforcement
    Examine the export_tips_to_csv function and any hooks that call it (such as admin_init, wp_ajax, or wp_ajax_nopriv). Look for current_user_can(), check_admin_referer(), or similar authorization checks within or before the function is invoked.
    Affected if No capability check (like current_user_can) is found before the export_tips_to_csv function executes, meaning any user (including unauthenticated) can trigger it.
  5. Verify unauthenticated access is possible
    If the site allows front-end access or has known AJAX endpoints, attempt to access the export function without logging in. Alternatively, check if the plugin registers any hooks with 'nopriv' capability (e.g., wp_ajax_nopriv_export_tips_to_csv) which would allow unauthenticated invocation.
    Affected if The export action is reachable without authentication, or an AJAX hook is registered with nopriv handling for the export function.

A user is affected if the Order Tip for WooCommerce plugin is installed with a version before 1.3.2 AND the export_tips_to_csv function lacks capability checks, allowing unauthenticated access to export sensitive order tip data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.3.2 or later which includes the missing capability check. If an update is unavailable, consider disabling the plugin or implementing web application firewall rules to block unauthorized access to the export endpoint.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1119 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1119 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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