CVE-2024-33274
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 · uneditedDirectory Traversal vulnerability in FME Modules customfields v.2.2.7 and before allows a remote attacker to obtain sensitive information via the Custom Checkout Fields, Add Custom Fields to Checkout parameter of the ajax.php
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 confidenceDirectory traversal vulnerability in FME Modules customfields plugin's ajax.php allows remote attackers to read arbitrary files on the server via path traversal sequences in the Add Custom Fields to Checkout parameter, potentially exposing configuration files, credentials, and other sensitive system files.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify FME Modules customfields plugin installationLocate the customfields plugin directory in the web root (commonly at /wp-content/plugins/fme-customfields/ or similar paths depending on the CMS). Check for the presence of ajax.php within the plugin folder.Affected if The plugin folder and ajax.php file exist on the server.
-
Determine plugin versionCheck the main plugin file (typically customfields.php or readme.txt) for the version number declared in the plugin header metadata. Compare this version against the vendor's release notes for CVE-2024-33274.Affected if The installed version is older than the patched version released for this CVE.
-
Verify ajax.php endpoint is web-accessibleAttempt a direct HTTP request to the ajax.php endpoint (e.g., GET /wp-content/plugins/fme-customfields/ajax.php). Confirm the file responds to HTTP requests.Affected if The ajax.php file is publicly accessible without authentication.
-
Inspect the Add Custom Fields to Checkout parameterReview the plugin configuration panel for the 'Add Custom Fields to Checkout' feature. Determine if this functionality is enabled or exposed through the ajax.php interface.Affected if The Add Custom Fields to Checkout feature is enabled and accessible via the vulnerable ajax.php endpoint.
-
Review server access logs for path traversal attemptsSearch web server access logs (Apache, Nginx) for requests to ajax.php containing '../' sequences, especially targeting the Add Custom Fields to Checkout parameter.
A user is affected if the FME Modules customfields plugin is installed, the ajax.php endpoint is accessible, and the Add Custom Fields to Checkout feature is enabled without a patch for CVE-2024-33274.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to a patched version of the plugin; if no update is available, disable the plugin. Apply web server rules to block path traversal sequences (../) in requests as a temporary measure until the plugin is updated.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-33274 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-33274 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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