CVE-2023-37749
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIncorrect access control in the REST API endpoint of HubSpot v1.29441 allows unauthenticated attackers to view users' data without proper authorization.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceHubSpot v1.29441 contains an incorrect access control vulnerability in a REST API endpoint. The endpoint fails to properly enforce authorization checks, allowing unauthenticated attackers to access and view sensitive user data by directly referencing object identifiers without validation of the requester's permissions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify HubSpot installation and versionLocate the HubSpot instance and determine the installed version number (v1.29441 or nearby versions in the v1.x line). Check the application's about page, version file, or API response headers for version information.Affected if The installed version matches or is close to v1.29441 (the vulnerable release).
-
Confirm REST API endpoint exposureIdentify whether the HubSpot REST API endpoints are externally accessible. Check network configuration, firewall rules, and API gateway settings to determine if the API is reachable from untrusted networks.Affected if The REST API endpoint is publicly accessible without authentication barriers.
-
Verify authorization is not enforced on the endpointSend a direct request to the REST API endpoint referencing object identifiers (such as user IDs or object IDs) without providing authentication credentials. Observe whether the request is accepted and returns sensitive data.Affected if The API returns user data or sensitive information without requiring valid authentication or authorization tokens.
-
Test object-level access controlAttempt to access different user object identifiers through the API endpoint using an unauthenticated or unauthorized request. Compare whether access is granted to objects the requester should not have permission to view.Affected if Unauthenticated or unauthorized requests successfully retrieve data for object identifiers they should not have access to.
You are affected if your HubSpot installation is version v1.29441 (or a related v1.x version) and the REST API endpoint allows unauthenticated access to sensitive user data by directly referencing object identifiers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper authentication and authorization checks on the affected REST API endpoint to ensure users can only access data they are explicitly permitted to view. Validate user identity for all API requests and enforce object-level access control.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37749 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-37749 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data