dbcve.org
CampressWordPress extension · Apuswp

CVE-2024-10763

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-13
Fix available
A fix is available. Upgrade to after 1.35 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Campress theme for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.35 via the 'campress_woocommerce_get_ajax_products' function. This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where php file type can be uploaded and included.

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 Campress theme for WordPress versions up to 1.35 contains a Local File Inclusion vulnerability in the campress_woocommerce_get_ajax_products function. Unauthenticated attackers can exploit this to include arbitrary files and execute any PHP code present in those files, potentially achieving full server compromise.

MitigationUpdate the Campress theme to version 1.36 or later where the vulnerability is patched. If an update is unavailable, implement strict input validation and path traversal protection in the vulnerable function, or temporarily disable the affected functionality.

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
CampressWordPress extension
Affected:<= 1.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 Campress theme is installed
    Check WordPress themes directory (wp-content/themes/) for the campress folder, or query WordPress database: SELECT * FROM wp_options WHERE option_name = 'template' OR option_name = 'stylesheet';
    Affected if The campress folder exists in themes directory or theme is set as active template/stylesheet
  2. Determine installed Campress version
    Check theme style.css header in wp-content/themes/campress/style.css for 'Version:' field, or check version defined in theme's functions.php or main class file
    Affected if Version is 1.35 or lower, or version field is missing entirely (indicating very old unversioned release)
  3. Verify WooCommerce integration is enabled
    Check if WooCommerce plugin is active and Campress WooCommerce modules are enabled. Look for files like woocommerce.php, includes/woocommerce.php, or WooCommerce-related settings in theme options
    Affected if WooCommerce is active and Campress WooCommerce functionality is enabled, as the vulnerable function name contains 'woocommerce'
  4. Locate the vulnerable function file
    Search theme files for 'campress_woocommerce_get_ajax_products' function definition, typically in includes/ajax.php, functions.php, or similar includes directory within the theme
    Affected if The function exists in the theme codebase and accepts user-supplied file path parameters without proper sanitization

User is affected if Campress theme version is 1.35 or lower AND WooCommerce integration is enabled AND the vulnerable ajax function is present in the codebase.

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
Upgrade available Upgrade to a release after 1.35
Interim mitigation

Update the Campress theme to version 1.36 or later where the vulnerability is patched. If an update is unavailable, implement strict input validation and path traversal protection in the vulnerable function, or temporarily disable the affected functionality.

Fix this in Campress Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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