dbcve.org
EmbedaiApplication · Thesamur

CVE-2025-0745

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 the backups of the database by requesting the "/embedai/app/uploads/database/<SQL_FILE>" endpoint.

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 · moderate confidence

Improper Access Control vulnerability in EmbedAI 2.1 and below allows authenticated users to directly access database backup files by requesting the /embedai/app/uploads/database/<SQL_FILE> endpoint, bypassing intended access restrictions on sensitive SQL backup files.

MitigationImplement proper authorization checks to verify user permissions before serving files from the database uploads directory, and consider moving database backups outside the web-accessible directory or restricting access to admin-only roles.

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 the installed EmbedAI version
    Check the application version displayed in the product UI, configuration files, or any version metadata file included with the installation
    Affected if The version is 2.1 or any version below 2.1 (e.g., 2.0.x, 1.x)
  2. Verify the vulnerable endpoint path exists
    Inspect the web server document root for the path /embedai/app/uploads/database/ - look for a 'database' subdirectory under the uploads folder
    Affected if The directory /embedai/app/uploads/database/ exists and is web-accessible
  3. Check for SQL backup files in the uploads directory
    List or enumerate files in the /embedai/app/uploads/database/ directory - look for .sql files that appear to be database backups
    Affected if Any .sql backup files are present in this directory
  4. Test direct access to backup files
    As an authenticated (non-admin) user, attempt to directly access the URL /embedai/app/uploads/database/<filename>.sql - where <filename>.sql is a backup file found in the directory
    Affected if The request succeeds and the file content is returned without proper authorization check
  5. Verify access control configuration
    Review the application's access control settings or middleware configuration to determine if the /embedai/app/uploads/database/ path has role-based restrictions
    Affected if No role-based access restrictions are configured for the database uploads directory

If you are running EmbedAI version below 2.1 and the /embedai/app/uploads/database/ directory with .sql files is accessible to authenticated users without proper authorization, you are affected by this vulnerability.

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.

dbcve · scoped
Upgrade available Upgrade to 2.1 or later
Fixed in 2.1
Interim mitigation

Implement proper authorization checks to verify user permissions before serving files from the database uploads directory, and consider moving database backups outside the web-accessible directory or restricting access to admin-only roles.

Recommended fix Moderate confidence

EmbedAI version 2.1 or later

  1. 1. Identify the current installed version of EmbedAI by checking the application configuration or dashboard.
  2. 2. Obtain the latest stable release of EmbedAI (version 2.1 or later) from the official vendor repository.
  3. 3. Before upgrading, perform a full backup of the current installation including database and configuration files.
  4. 4. Upgrade the EmbedAI installation to version 2.1 or the latest stable release.
  5. 5. After upgrade, verify the access control fix by confirming that the /embedai/app/uploads/database/ endpoint is properly protected and requires appropriate authorization.
  6. 6. Test that legitimate database backup functionality still works for authorized users only.

Generated from the published advisory — verify against the referenced sources before acting.

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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