# CVE-2024-33274: Path traversal in n/a

> A remote attacker can exploit a directory traversal flaw in the FME Modules customfields plugin to access sensitive information via the ajax.php endpoint.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Apr 2024
- **Updated:** 6 Sep 2024
- **Also known as:** GHSA-7v7g-vx57-pg3r

## What is CVE-2024-33274?

CVE-2024-33274 is a high-severity path traversal vulnerability in n/a, published on 30 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory 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

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2024-33274?


## How do I fix CVE-2024-33274?

No fix has been published for CVE-2024-33274 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-33274 being exploited?

There is no known exploitation of CVE-2024-33274 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-33274 and fix it if it is affected.

What it is: CVE-2024-33274 is a high-severity path traversal vulnerability in n/a, published on 30 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-33274 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-33274/ (Markdown: https://insights.sbomify.com/CVE-2024-33274/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-33274
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-33274
- OSV: https://osv.dev/vulnerability/CVE-2024-33274

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-33274/
Summaries are generated and may contain mistakes; the official description above is the record.