# CVE-2025-34293: GN4 Publishing System Insecure Direct Object Reference (IDOR) Information Disclosure

> Authenticated users can access sensitive account data for other users via API, potentially leading to account takeover.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Oct 2025
- **Updated:** 14 May 2026
- **Also known as:** GHSA-x7wc-2853-87fv

## What is CVE-2025-34293?

CVE-2025-34293 is a high-severity vulnerability in Naviga Global / Miles 33 GN4 Publishing System, published on 24 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

GN4 Publishing System versions prior to 2.6 contain an insecure direct object reference (IDOR) vulnerability via the API. Authenticated requests to the API's object endpoints allow an authenticated user to request arbitrary user IDs and receive sensitive account data for those users, including the stored password and the account's security question and answer. The exposed recovery data and encrypted password may be used to reset or take over the target account.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2025-34293?


## How do I fix CVE-2025-34293?

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

## Is CVE-2025-34293 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-34293 and fix it if it is affected.

What it is: CVE-2025-34293 is a high-severity vulnerability in Naviga Global / Miles 33 GN4 Publishing System, published on 24 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-34293 in the wild and no public exploit code.

Affected product: Naviga Global / Miles 33 GN4 Publishing System. 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-2025-34293/ (Markdown: https://insights.sbomify.com/CVE-2025-34293/index.md)
```

## Sources

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

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