dbcve.org
SaradaWordPress extension · Blossomthemes

CVE-2024-31429

HIGH · 8.8 CVSS v3.1 Published 2024-04-15
Fix available
A fix is available. Upgrade to 1.1.3 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 Blossom Themes Sarada Lite.This issue affects Sarada Lite: from n/a through 1.1.2.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Sarada Lite WordPress theme allows remote attackers to trick authenticated users into submitting unintended requests to the site. The theme lacks proper anti-CSRF token validation on state-changing operations, enabling attackers to execute actions on behalf of authenticated administrators or users.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all forms and AJAX actions that perform state changes, and verify the nonce validity server-side before processing requests.

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
SaradaWordPress extension
Affected:< 1.1.3

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. Confirm Sarada Lite theme is installed
    Navigate to Appearance > Themes in WordPress admin dashboard and look for the Sarada Lite theme in the installed themes list
    Affected if The Sarada Lite theme appears in the installed themes
  2. Check installed theme version
    Click on the Sarada Lite theme to view its details, or check the style.css file in the theme directory for the 'Version:' header
    Affected if The version number displayed is less than 1.1.3 (e.g., 1.1.2, 1.1.1, 1.0.x)
  3. Verify theme is active
    In Appearance > Themes, confirm the Sarada Lite theme has the 'Active' badge or is currently selected as the active theme
    Affected if The Sarada Lite theme is currently active on the site
  4. Identify state-changing operations in theme code
    Examine PHP files in the theme directory (typically /wp-content/themes/sarada-lite/) for form tags, AJAX handlers (wp_ajax_), and POST/GET request handling that perform changes to site data
    Affected if State-changing forms or AJAX actions exist in the theme without nonce verification using wp_verify_nonce or check_admin_referer
  5. Inspect nonce implementation on forms
    Search theme files for 'nonce' or '_wpnonce' strings in form definitions and AJAX callbacks; verify that nonces are generated with wp_create_nonce or wp_nonce_field and validated with wp_verify_nonce before processing
    Affected if Forms or AJAX actions in the theme lack nonce field generation or server-side nonce validation

You are affected if the Sarada Lite theme version is below 1.1.3 and the theme is active with state-changing operations that do not implement WordPress nonce verification.

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.1.3 or later
Fixed in 1.1.3
Interim mitigation

Implement WordPress nonces (anti-CSRF tokens) on all forms and AJAX actions that perform state changes, and verify the nonce validity server-side before processing requests.

Recommended fix Moderate confidence

Sarada Lite 1.1.3

  1. Log in to the WordPress admin dashboard
  2. Navigate to Appearance > Themes
  3. If there is an update available for Sarada Lite, click 'Update Now' to update to the latest version
  4. Alternatively, download Sarada Lite version 1.1.3 from the official source (Blossom Themes or WordPress.org theme repository)
  5. Go to Themes > Add New > Upload Theme
  6. Upload the new version 1.1.3 and replace the existing installation
  7. Verify the theme version after update by checking Appearance > Themes

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

Fix this in Sarada Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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