CVE-2025-0747
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 Stored Cross-Site Scripting vulnerability has been found in EmbedAI. This vulnerability allows an authenticated attacker to inject a malicious JavaScript code into a message that will be executed when a user opens the chat.
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 stored Cross-Site Scripting vulnerability in EmbedAI allows authenticated attackers to inject malicious JavaScript into chat messages. When other users open or view the affected chat, the injected script executes in their browser context, potentially allowing session hijacking, credential theft, or defacement.
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 EmbedAI versionLocate the application version file or check the admin dashboard for the current software version. Common locations include version.php, package.json, or the admin settings page.Affected if The installed version is Thesamur EmbedAI and the version number is less than 2.1
-
Verify the application has user authentication enabledCheck the application configuration or settings to confirm that user authentication is enabled and functional.Affected if User authentication is required for the XSS to be exploitable, so authentication must be enabled for the vulnerability to pose a risk
-
Determine if the chat messaging feature is activeReview the application modules or feature list to confirm that the chat messaging functionality is installed and accessible to users.Affected if The chat messaging feature must be enabled and accessible to users for the stored XSS to be triggered
-
Inspect stored chat messages for unsanitized contentAccess the chat message database or message storage logs and examine recent messages for any HTML tags, script tags, or JavaScript event handlers that may have been stored without sanitization.Affected if Any chat messages contain unescaped HTML, script tags, or javascript: URIs in user-submitted content
-
Test for XSS by viewing chat messages in a different browser contextCreate a test chat session, send a benign XSS probe message containing characters like <script>alert(1)</script> or an img onerror tag, then view that message from a separate user account to observe if the script executes.Affected if The XSS probe executes and triggers an alert or executes JavaScript when viewed by another user
A user is affected if they are running Thesamur EmbedAI version less than 2.1 with authentication and the chat messaging feature enabled, and if chat messages are not being sanitized before storage.
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 context-aware output encoding and input validation/sanitization on all user-supplied message content before storage and upon display. Use a security-focused HTML sanitization library to strip dangerous HTML/script tags.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0747 — 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-0747 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