CVE-2025-0746
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 · uneditedA Reflected Cross-Site Scripting vulnerability has been found in EmbedAI 2.1 and below. This vulnerability allows an authenticated attacker to craft a malicious URL leveraging the"/embedai/users/show/<SCRIPT>" endpoint to inject the malicious JavaScript code. This JavaScript code will be executed when a user opens the malicious URL.
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 confidenceA reflected Cross-Site Scripting (XSS) vulnerability exists in EmbedAI 2.1 and below in the /embedai/users/show/<SCRIPT> endpoint. The application fails to properly sanitize or encode user-supplied input in the URL path, allowing authenticated attackers to inject malicious JavaScript code that executes in victims' browsers when they access the crafted URL.
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< 2.1CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 the installed productCheck application files, banners, or admin interface for the product name. Look for 'EmbedAI' or 'Thesamur EmbedAI' identification strings in the application.Affected if The product is not Thesamur EmbedAI or cannot be identified as EmbedAI.
-
Determine the installed versionCheck the application version number in the admin panel, configuration files, or by querying the application metadata (such as package.json, version info in footer, or API endpoint). Compare against the affected range: versions below 2.1.Affected if The installed version is 2.1 or lower (any version below 2.1).
-
Verify the vulnerable endpoint existsCheck if the /embedai/users/show/ endpoint is accessible in the application by reviewing URL routing configuration or attempting to access the path.Affected if The /embedai/users/show/ endpoint exists and responds to requests.
-
Confirm authentication mechanism is configuredReview the application authentication settings, user management configuration, or session handling to determine if authentication is required to access the affected endpoint.Affected if Authentication is enabled and the attacker can obtain valid credentials to reach the endpoint.
A user is affected if they are running Thesamur EmbedAI version 2.1 or below, the /embedai/users/show/ endpoint exists, and authentication is configured allowing access to the endpoint.
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 data2.1
Implement robust input validation and output encoding on the affected endpoint to neutralize XSS payloads. The application should sanitize or properly encode any user-supplied input before reflecting it in the HTTP response.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0746 — 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-2025-0746 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