dbcve.org
Construction Landing PageWordPress extension · Rarathemes

CVE-2024-37508

HIGH · 8.8 CVSS v3.1 Published 2025-01-02
Fix available
A fix is available. Upgrade to 1.3.6 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 Construction Landing Page construction-landing-page allows Cross Site Request Forgery.This issue affects Construction Landing Page: from n/a through <= 1.3.5.

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

A Cross-Site Request Forgery (CSRF) vulnerability exists in the raratheme Construction Landing Page WordPress theme (versions up to 1.3.5). The theme lacks proper anti-CSRF token validation on state-changing operations, allowing authenticated administrators to be tricked into performing unintended actions (such as modifying theme settings) via maliciously crafted requests from other sites.

MitigationUpdate the Construction Landing Page theme to the latest version which should include anti-CSRF protection. If no update is available, add WordPress nonces to all forms and AJAX requests, and validate nonce verification on the server side for all state-changing operations.

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
Construction Landing PageWordPress extension
Affected:< 1.3.6

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 if Construction Landing Page theme is installed
    Navigate to Appearance > Themes in WordPress admin panel, or check the /wp-content/themes/ directory for a folder named 'construction-landing-page' or similar Rarathemes folder
    Affected if The theme folder exists in the WordPress themes directory
  2. Confirm the installed theme version
    Access the theme's main style.css file (usually at /wp-content/themes/[theme-folder]/style.css) and locate the 'Version:' header in the file comments, or view theme details in WordPress admin under Appearance > Themes
    Affected if The version number displayed is lower than 1.3.6 (e.g., 1.3.5, 1.3.4, etc.)
  3. Verify the theme is active on the site
    In WordPress admin, go to Appearance > Themes and check if Construction Landing Page is the currently active theme
    Affected if The theme shows as 'Active' or 'Enabled'
  4. Inspect theme code for nonce implementation
    Examine PHP files in the theme folder (especially functions.php, customizer.php, or any file handling form submissions) and search for 'wp_nonce_field' or 'wp_nonce_url' function calls around form definitions, and check for 'check_admin_referer' or 'wp_verify_nonce' calls in form processing code
    Affected if No nonce verification functions are found in files handling state-changing operations (settings saves, option updates, etc.)

Your environment is affected if the Construction Landing Page theme is active with a version below 1.3.6 and the theme code lacks proper nonce validation for state-changing operations.

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.3.6 or later
Fixed in 1.3.6
Interim mitigation

Update the Construction Landing Page theme to the latest version which should include anti-CSRF protection. If no update is available, add WordPress nonces to all forms and AJAX requests, and validate nonce verification on the server side for all state-changing operations.

Recommended fix High confidence

Construction Landing Page version 1.3.6

  1. Backup your WordPress site database and files before making any changes
  2. Log in to WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Locate the 'Construction Landing Page' by raratheme plugin
  5. Click 'Update now' if an update to version 1.3.6 is available, or deactivate the plugin and reinstall version 1.3.6
  6. Verify the plugin version is now 1.3.6 in the plugins list
  7. Test that the plugin functionality works as expected after the update
Caveat No breaking changes reported in the available vulnerability documentation

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

Fix this in Construction Landing Page Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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