dbcve.org
CalliopeWordPress extension · Extendthemes

CVE-2024-2904

HIGH · 8.8 CVSS v3.1 Published 2024-03-26
Fix available
A fix is available. Upgrade to 1.0.35 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 Extend Themes Calliope.This issue affects Calliope: from n/a through 1.0.33.

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 Calliope WordPress theme allows attackers to trick authenticated users into submitting unintended requests, potentially leading to unauthorized configuration changes or actions within the theme settings.

MitigationImplement anti-CSRF tokens (nonces) for all state-changing operations and form submissions in the theme, and verify the Referer/Origin headers on POST 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
CalliopeWordPress extension
Affected:< 1.0.35

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 Calliope theme version
    Locate the Calliope theme folder in wp-content/themes/calliope/ and open style.css. Look for the 'Version:' declaration near the file header, or check the theme version displayed in WordPress Admin > Appearance > Themes.
    Affected if The version number is less than 1.0.35
  2. Inspect theme form submissions for nonce presence
    Search theme PHP files (especially in includes/ or classes/ subdirectories) for form handling code. Look for occurrences of wp_nonce_field, wp_verify_nonce, or check_admin_referer in files that handle settings or configuration forms.
    Affected if State-changing forms (settings pages, options panels) are missing nonce verification calls, or nonces are not being validated before processing submissions
  3. Verify Referer/Origin header validation on POST handlers
    Examine PHP files that process POST requests (typically in functions.php, class files, or admin controllers). Search for $_SERVER['HTTP_REFERER'] or $_SERVER['HTTP_ORIGIN'] usage with conditional validation logic.
    Affected if POST request handlers do not verify the Referer or Origin headers to confirm the request originated from the legitimate site
  4. Review all admin action handlers
    Search theme files for add_action hooks tied to admin_init, admin_post, or similar WordPress admin hooks. Check if these handlers validate user permissions and nonce tokens before executing state-changing operations.
    Affected if Action handlers exist that modify theme settings, options, or configuration without proper CSRF token validation

The environment is affected if the Calliope theme version is below 1.0.35 AND the theme contains forms or admin actions that lack nonce token validation and Referer/Origin header checks.

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.0.35 or later
Fixed in 1.0.35
Interim mitigation

Implement anti-CSRF tokens (nonces) for all state-changing operations and form submissions in the theme, and verify the Referer/Origin headers on POST requests.

Recommended fix High confidence

1.0.35

  1. 1. Create a complete backup of your WordPress site, including the database and all theme files.
  2. 2. Navigate to Appearance > Themes in your WordPress admin dashboard.
  3. 3. Locate the Calliope theme and check the current version to confirm it is below 1.0.35.
  4. 4. Update the Calliope theme to version 1.0.35 or later by clicking the Update button or uploading the new version.
  5. 5. Verify the update was successful by confirming the theme version now shows 1.0.35 or higher.
  6. 6. Test critical functionality on your site to ensure the update did not introduce any issues.

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

Fix this in Calliope 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-2904 — 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-2904 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