dbcve.org
EmbedaiApplication · Thesamur

CVE-2025-0739

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-30
Fix available
A fix is available. Upgrade to 2.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
An Improper Access Control vulnerability has been found in EmbedAI 2.1 and below. This vulnerability allows an authenticated attacker to show subscription's information of others users by changing the "SUSCBRIPTION_ID" param of the endpoint "/demos/embedai/subscriptions/show/<SUSCBRIPTION_ID>".

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 confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability where an authenticated attacker can access other users' subscription information by manipulating the subscription ID parameter in the /demos/embedai/subscriptions/show/<SUSCBRIPTION_ID> endpoint. The application fails to verify that the requesting user owns or has permission to access the specified subscription resource.

MitigationImplement proper authorization checks to validate that the authenticated user owns or has permission to access the requested subscription before returning any data. Consider using indirect object references and enforcing row-level access control on subscription resources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EmbedaiApplication
Affected:< 2.1

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed version of Thesamur Embedai
    Locate the application version file, typically found in the application root directory (e.g., version.php, package.json, or a config file). Check the version number displayed in the admin panel under 'About' or 'System Info'.
    Affected if The installed version is Thesamur Embedai and the version number is less than 2.1 (e.g., 2.0.x, 1.x, etc.)
  2. Verify the subscriptions endpoint exists
    Check if the URL path /demos/embedai/subscriptions/show/ is accessible in the application. This can be done by attempting to access the endpoint directly via a web browser or by examining the application's routing configuration.
    Affected if The /demos/embedai/subscriptions/show/<ID> endpoint exists and responds to requests, even with a valid subscription ID
  3. Confirm subscription feature is enabled
    Check the application's configuration files or admin settings to determine if the subscription management feature is enabled. Look for settings related to user subscriptions, paid plans, or membership features.
    Affected if The subscription module is active and users can create or manage subscriptions in the application
  4. Test for missing authorization on subscription access
    Create or use two different user accounts. Log in as User A, access a subscription owned by User A (note its subscription ID). Then log in as User B and attempt to access the same subscription ID via /demos/embedai/subscriptions/show/<SUBSCRIPTION_ID>. Inspect the response to see if User B can view User A's subscription details.
    Affected if User B can successfully retrieve subscription details belonging to User A without receiving a 403 Forbidden or 'Access Denied' error, indicating the application does not verify ownership before returning subscription data

A user is affected if they are running Thesamur Embedai version less than 2.1 with the subscriptions feature enabled, and the application allows a user to access another user's subscription data by manipulating the subscription ID in the URL.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 2.1 or later
Fixed in 2.1
Interim mitigation

Implement proper authorization checks to validate that the authenticated user owns or has permission to access the requested subscription before returning any data. Consider using indirect object references and enforcing row-level access control on subscription resources.

Fix this in Embedai Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0739 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0739 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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