dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-11926

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Travel Booking WordPress Theme theme for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the '__stPartnerCreateServiceRental', 'st_delete_order_item', '_st_partner_approve_booking', 'save_order_item', and '__userDenyEachInfo' functions in all versions up to, and including, 3.1.6. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify posts, delete posts and pages, approve arbitrary orders, insert orders with arbitrary prices, and deny user information.

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 Travel Booking WordPress Theme lacks proper capability checks on five functions ('__stPartnerCreateServiceRental', 'st_delete_order_item', '_st_partner_approve_booking', 'save_order_item', and '__userDenyEachInfo'), allowing any authenticated user with Subscriber-level access to perform administrative actions including post modification/deletion, order approval, price manipulation, and user information denial.

MitigationUpdate the theme to version 3.1.7 or later which includes proper capability checks. If no update is available, add WordPress capability checks (e.g., current_user_can('manage_options')) to each of the five affected functions to verify user permissions before executing sensitive operations.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Travel Booking Theme is installed
    Check the wp-content/themes directory for a theme folder named 'travel-booking' or similar. Look for style.css with 'Theme Name: Travel Booking' in the header.
    Affected if The Travel Booking theme is present in the WordPress installation.
  2. Identify the installed theme version
    Open the theme's style.css file and locate the 'Version:' declaration in the theme header comment. Compare this version against 3.1.7.
    Affected if The installed version is lower than 3.1.7.
  3. Locate the vulnerable AJAX action handlers
    Search the theme's functions.php and any ajax-related files for the five function names: '__stPartnerCreateServiceRental', 'st_delete_order_item', '_st_partner_approve_booking', 'save_order_item', and '__userDenyEachInfo'. These are typically hooked via add_action('wp_ajax_...', 'function_name').
    Affected if Any of these five functions exist in the theme without proper capability checks.
  4. Verify capability checks exist before vulnerable functions
    Open each of the five identified function files and search for permission checks such as current_user_can('manage_options') or current_user_can('edit_posts') immediately before the sensitive operations (post modification, order approval, price changes, user denial actions).
    Affected if The functions execute without any current_user_can() permission verification, or only check for subscriber-level access.
  5. Test if Subscriber-level users can access admin actions
    Using a test Subscriber account, attempt to access the AJAX endpoints or observe if the theme allows post/order manipulation via its frontend or backend interfaces available to subscribers.
    Affected if A Subscriber-level user can modify posts, approve orders, change prices, or deny user information through the theme functionality.

A user is affected if the Travel Booking theme is installed with a version lower than 3.1.7 and the five vulnerable functions lack proper capability checks, allowing Subscriber-level users to perform administrative actions.

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 theme to version 3.1.7 or later which includes proper capability checks. If no update is available, add WordPress capability checks (e.g., current_user_can('manage_options')) to each of the five affected functions to verify user permissions before executing sensitive operations.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11926 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-11926 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