LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69752: An issue in the "My Details" user profile functionality of Ideagen Q-Pulse 7.1.0.32 allows an authenticated...

An issue in the "My Details" user profile functionality of Ideagen Q-Pulse 7.1.0.32 allows an authenticated user to view other users' profile information by modifying the objectKey HTTP parameter in the My Details page URL.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-69752 is a privacy exposure in Ideagen Q-Pulse 7.1.0.32. A logged-in user may be able to view other users' profile details through the My Details function. The issue is limited to confidentiality in the provided scoring, but it can still expose employee or account information.

Executive priority

Treat this as a moderate-priority privacy and access-control issue. It does not indicate unauthenticated compromise, but affected deployments could leak internal user profile data to ordinary authenticated users.

Technical view

The CVE describes CWE-639, authorization bypass through a user-controlled key. In the My Details profile URL, the objectKey HTTP parameter can be changed so an authenticated user can access another user's profile information. The listed CVSS is 4.3, with network access, low complexity, low privileges, no user interaction, and low confidentiality impact.

Likely exposure

Organizations running Ideagen Q-Pulse 7.1.0.32 are the only clearly named exposure. The structured affected-product data is incomplete, so confirm product and version directly in asset inventory.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Abuse requires an authenticated account and targets profile information, not code execution, system takeover, or service disruption based on the supplied evidence.

Researcher notes

Evidence is narrow: the description names Ideagen Q-Pulse 7.1.0.32, while structured affected fields are marked n/a. No patch version, workaround, exploit activity, or affected CPEs are provided in the source bundle.

Mitigation direction

  • Check Ideagen or advisory guidance for a fixed version or vendor-approved workaround.
  • Limit Q-Pulse accounts to users with a current business need.
  • Review role assignments and remove stale or overprivileged accounts.
  • Restrict Q-Pulse network access where business operations allow.
  • Monitor profile-page requests for unusual access patterns or user enumeration.

Validation and detection

  • Inventory Q-Pulse deployments and confirm whether version 7.1.0.32 is present.
  • Review application access-control logic for My Details profile object identifiers.
  • Check logs for repeated profile lookups across different user records.
  • Validate remediation in a controlled test environment before production rollout.
Prepared
Confidence
medium
Sources
3

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-69752 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N2.81.4CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2025-69752Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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.