dbcve.org
EmbedaiApplication · Thesamur

CVE-2025-0742

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 obtain files stored by others users by changing the "FILE_ID" of the endpoint "/embedai/files/show/<FILE_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

An Improper Access Control (IDOR) vulnerability in EmbedAI 2.1 and below allows authenticated users to access files belonging to other users by manipulating the FILE_ID parameter in the /embedai/files/show/<FILE_ID> endpoint. The application fails to verify that the requesting user owns or has permission to access the specific file.

MitigationImplement proper authorization checks to verify file ownership or permissions before serving file content, ensuring users can only access files they own or are explicitly authorized to view.

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 EmbedAI version
    Locate the application version number in the software installation, typically found in the admin panel, about page, or version file (e.g., version.php, package.json, or similar).
    Affected if The installed version is Thesamur EmbedAI and the version number is below 2.1 (e.g., 2.0, 1.x)
  2. Confirm file upload feature is enabled
    Check if the file upload/storage functionality is active in the application configuration or admin settings. Look for file upload permissions in the user role or access control settings.
    Affected if File upload feature is enabled and users can upload or access files through the application
  3. Verify the vulnerable endpoint exists
    Check if the /embedai/files/show/<FILE_ID> endpoint is accessible in the application. This is typically found in the web application's routing configuration or by reviewing the application's URL structure.
    Affected if The /embedai/files/show/ endpoint exists and accepts FILE_ID parameters
  4. Review file access authorization controls
    Examine the application's source code or configuration for authorization logic around file retrieval. Look for code that validates user ownership of files before serving content in the file download/show functionality.
    Affected if No ownership verification is performed before serving file content, or the code only checks authentication without verifying file ownership
  5. Test file access boundary (if authorized)
    Using two different authenticated user accounts, attempt to access a file owned by one user while authenticated as the other, by manipulating the FILE_ID parameter in the URL.
    Affected if User A can successfully view or download a file belonging to User B by simply changing the FILE_ID value

The environment is affected if running Thesamur EmbedAI version below 2.1 with the file upload/download feature enabled and the application lacks proper ownership verification on the /embedai/files/show/ endpoint.

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 verify file ownership or permissions before serving file content, ensuring users can only access files they own or are explicitly authorized to view.

Fix this in Embedai Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0742 — 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-0742 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