CVE-2025-34293: GN4 Publishing System Insecure Direct Object Reference (IDOR) Information Disclosure
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.
Security readout for executives and security teams
Plain-English summary
CVE-2025-34293 is a high-severity data exposure flaw in GN4 Publishing System before version 2.6. A logged-in user can request other users’ account records through the API and receive sensitive recovery data and an encrypted stored password. This creates credible account takeover risk for publishing environments using affected GN4 deployments.
Executive priority
Treat as urgent for any organization using GN4 before 2.6. The business risk is unauthorized access to newsroom or publishing accounts, possible account takeover, and exposure of sensitive recovery data. Prioritize version validation, vendor remediation, and access review.
Technical view
The issue is an API insecure direct object reference, CWE-639. Authenticated network access with low privileges can retrieve arbitrary user IDs from object endpoints, exposing sensitive account data including stored password, security question, and answer. CVSS v4.0 is 8.6 high, with high confidentiality and integrity impact, no user interaction, and no availability impact.
Likely exposure
Exposure is limited to organizations running Naviga Global / Miles 33 GN4 Publishing System versions before 2.6. Risk is higher where the GN4 API is reachable by broad internal users, contractors, partners, VPN users, or the internet. The sources do not confirm default internet exposure.
Exploitation context
The CVE and advisory describe abuse by an authenticated user, not anonymous access. The vulnerability can support account reset or takeover using exposed recovery data. The source bundle does not show CISA KEV listing or confirmed active exploitation.
Researcher notes
Evidence is sufficient for high risk, but some affected-version metadata is sparse: the bundle lists versions prior to 2.6 in prose while the affected entry shows “0.” Validate against vendor records and the VulnCheck advisory. Avoid assuming exploit availability or active exploitation without additional evidence.
Mitigation direction
Confirm whether GN4 is in use and identify deployed versions.
Upgrade GN4 deployments prior to 2.6 to a vendor-supported fixed release.
Check Naviga or Miles 33 guidance for exact remediation instructions.
Restrict GN4 API access to trusted networks and required users.
Review and rotate exposed credentials and account recovery data where compromise is suspected.
Validation and detection
Inventory GN4 instances and record exact version numbers.
Flag any GN4 version earlier than 2.6 for remediation.
Identify whether GN4 API endpoints are reachable externally or broadly internally.
Review API logs for authenticated access to other users’ account objects.
After remediation, verify users cannot access account records outside authorization.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-639 · source CWE mapping
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.