# CVE-2026-29098: SuiteCRM has Relative Path Traversal via ModuleBuilder Modules ExportCustom Action

> An administrator can exploit path traversal in ModuleBuilder to copy sensitive system files into the web root, exposing secrets.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** GHSA-6858-fhw5-56gf

## What is CVE-2026-29098?

CVE-2026-29098 is a medium-severity path traversal vulnerability in SuiteCRM, published on 19 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SuiteCRM is an open-source, enterprise-ready Customer Relationship Management (CRM) software application. Prior to versions 7.15.1 and 8.9.3, the `action_exportCustom` function in `modules/ModuleBuilder/controller.php` fails to properly neutralize path traversal sequences in the `$modules` and `$name` parameters. Both parameters later reach the `exportCustom` function in `modules/ModuleBuilder/MB/MBPackage.php` where they are both utilized in constructing s paths for file reading and writing. As such, it is possible for a user with access to the ModuleBuilder module, generally an administrator, to craft a request that can copy the content of any readable directory on the underlying host into the web root, making them readable. As the `ModuleBuilder` module is part of both major versions 7 and 8, both current major versions are affected. This vulnerability allows an attacker to copy any readable directory into the web root. This includes system files like the content of `/etc, or the root directory of the web server, potentially exposing secrets and environment variables. Versions 7.15.1 and 8.9.3 patch the issue.

Weakness: CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2026-29098?

It affects 1 product.


Products: Suitecrm Suitecrm.

## How do I fix CVE-2026-29098?

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

## Is CVE-2026-29098 being exploited?

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

## Other vulnerabilities in SuiteCRM

- [CVE-2026-29103](https://insights.sbomify.com/CVE-2026-29103/): SuiteCRM Vulnerable to Remote Code Execution via Module Loader Package Scanner Bypass (critical 9.1)
- [CVE-2026-29099](https://insights.sbomify.com/CVE-2026-29099/): SuiteCRM has Authenticated Blind SQL Injection in OutboundEmail Legacy Functionality. (high 8.8)
- [CVE-2026-33288](https://insights.sbomify.com/CVE-2026-33288/): SuiteCRM has Authenticated SQL Injection in Authentication Module (high 8.8)
- [CVE-2026-33289](https://insights.sbomify.com/CVE-2026-33289/): SuiterCRM has LDAP Filter Injection in Authentication Module (high 8.8)
- [CVE-2026-29109](https://insights.sbomify.com/CVE-2026-29109/): SuiteCRM Authenticated Remote Code Execution via Unsafe Deserialization in SavedSearch Filter Processing (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-29098 and fix it if it is affected.

What it is: CVE-2026-29098 is a medium-severity path traversal vulnerability in SuiteCRM, published on 19 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-29098 in the wild and no public exploit code.

Affected product: SuiteCRM. 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-2026-29098/ (Markdown: https://insights.sbomify.com/CVE-2026-29098/index.md)
```

## Sources

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

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