dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-9575

HIGH · 8.5 CVSS v4.0 Published 2024-10-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable

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
Local File Inclusion vulnerability in pretix Widget WordPress plugin pretix-widget on Windows allows PHP Local File Inclusion. This issue affects pretix Widget WordPress plugin: from 1.0.0 through 1.0.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

Local File Inclusion vulnerability in pretix Widget WordPress plugin versions 1.0.0-1.0.5 on Windows allows attackers to include arbitrary local PHP files via path traversal, potentially leading to remote code execution.

MitigationUpdate pretix Widget plugin to version 1.0.6 or later. Until patched, disable the plugin or implement WAF rules to block path traversal patterns in requests.

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

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
High
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:L/U:X

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. Verify pretix Widget plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'pretix Widget' in the list, or check the /wp-content/plugins/ directory for a folder named 'pretix-widget' or similar.
    Affected if The plugin appears in the installed plugins list.
  2. Check installed plugin version
    In WordPress admin > Plugins > Installed Plugins, click on 'pretix Widget' to view the version number, or read the main plugin PHP file header which contains the 'Version' field, or check the plugin folder for a style.css or readme.txt containing version info.
    Affected if The installed version is 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, or 1.0.5 (any version from 1.0.0 through 1.0.5 inclusive).
  3. Confirm plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify that pretix Widget shows 'Active' status under the plugin name.
    Affected if The plugin status shows as Active.
  4. Verify Windows host environment
    Check the server operating system by running 'systeminfo' on Windows or checking hosting provider documentation. The vulnerability specifically affects Windows deployments.
    Affected if The WordPress instance is hosted on a Windows server (IIS or Apache on Windows).
  5. Review access logs for path traversal attempts
    Examine web server access logs (IIS logs in C:\inetpub\logs\LogFiles or Apache logs on Windows) for requests containing patterns like '../', '..\', or absolute paths in parameters that might indicate exploitation attempts.
    Affected if Suspicious requests with path traversal patterns are found targeting the pretix Widget plugin endpoints.

You are affected if the pretix Widget plugin versions 1.0.0-1.0.5 are installed, active, and running on a Windows host.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update pretix Widget plugin to version 1.0.6 or later. Until patched, disable the plugin or implement WAF rules to block path traversal patterns in requests.

Recommended fix Moderate confidence

Upgrade to pretix Widget plugin version 1.0.6 or later

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Locate the 'pretix Widget' plugin
  4. 4. Check the current version number to confirm it is between 1.0.0 and 1.0.5
  5. 5. Click 'Update now' if an update is available, or manually download the latest version from the WordPress plugin repository
  6. 6. Verify the update was successful and the new version is installed
  7. 7. Test the plugin functionality to ensure it works correctly after the update

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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