Travel AgencyWordPress extension · Rarathemes

CVE-2024-37451

HIGH · 8.8 CVSS v3.1 Published 2025-01-02
Fix available
A fix is available. Upgrade to 1.5.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in raratheme Travel Agency travel-agency allows Cross Site Request Forgery.This issue affects Travel Agency: from n/a through <= 1.4.9.

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

Cross-Site Request Forgery (CSRF) vulnerability in the raratheme Travel Agency WordPress theme allows attackers to trick authenticated users into performing unintended actions. The theme fails to implement proper CSRF validation (nonces/tokens) on sensitive operations, enabling malicious requests to be processed when users visit attacker-controlled pages or click malicious links.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing operations including forms and AJAX endpoints. Validate Origin/Referer headers and configure SameSite attributes on session cookies.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Travel AgencyWordPress extension
Affected:< 1.5.0

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Identify installed theme version
    Locate and read the style.css file in the Travel Agency theme directory to find the Version header, or check the theme version displayed in WordPress admin under Appearance > Themes
    Affected if The installed version is below 1.5.0
  2. Inspect PHP files for nonce functions
    Search theme PHP files for wp_nonce_field, wp_nonce_url, check_admin_referer, or check_ajax_referer function calls to determine if CSRF tokens are implemented
    Affected if No nonce verification functions are found in theme PHP files handling sensitive operations
  3. Examine form templates for hidden nonce fields
    Review theme templates containing form elements (such as contact forms, booking forms, or settings forms) to check for hidden input fields containing nonce tokens
    Affected if Forms in the theme lack hidden nonce fields
  4. Check AJAX handlers for nonce verification
    Inspect any add_action calls for wp_ajax hooks in the theme and verify they call wp_verify_nonce or check_ajax_referer before processing requests
    Affected if AJAX endpoints do not verify nonce tokens before executing state-changing operations

The environment is affected if the Travel Agency theme version is lower than 1.5.0 and the theme lacks nonce implementation on forms and AJAX endpoints.

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.

dbcve · scoped
Upgrade available Upgrade to 1.5.0 or later
Fixed in 1.5.0
Interim mitigation

Implement anti-CSRF tokens (nonces) on all state-changing operations including forms and AJAX endpoints. Validate Origin/Referer headers and configure SameSite attributes on session cookies.

Recommended fix Moderate confidence

Travel Agency theme version 1.5.0

  1. Log in to WordPress admin dashboard
  2. Navigate to Appearance > Themes
  3. Locate the Travel Agency theme
  4. Click on the theme to view details
  5. If an update is available, click Update Now
  6. Alternatively, download Travel Agency version 1.5.0 from the official source (raratheme.com or WordPress theme repository) and upload via Appearance > Themes > Add New > Upload Theme
  7. Verify the theme version is 1.5.0 or later after update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Travel Agency 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 the upgrade done

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-37451 — 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-37451 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