dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2025-1794

MEDIUM · 5.4 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
The AM LottiePlayer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via uploaded SVG files in all versions up to, and including, 3.6.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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

The AM LottiePlayer WordPress plugin (versions up to 3.6.0) fails to properly sanitize SVG file uploads, allowing authenticated users with Author-level permissions or higher to embed malicious JavaScript within SVG files. When other users view pages containing these injected SVGs, the scripts execute in their browsers.

MitigationImplement strict input sanitization for SVG uploads using an allowlist approach and server-side validation, combined with proper output escaping when rendering SVG content. Upgrade to version 3.6.1 or later if available.

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

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
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 checks

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

  1. Verify AM LottiePlayer plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'AM LottiePlayer' in the list. Note whether it is active or inactive.
    Affected if The plugin is installed and active - the vulnerability only affects active installations processing user uploads.
  2. Check installed plugin version
    Click on the plugin name in the Plugins list to view details, or check the plugin main PHP file header for the Version field. Compare against the affected range (versions prior to 3.6.0).
    Affected if Installed version is earlier than 3.6.0 - these versions lack proper SVG sanitization and output escaping.
  3. Identify SVG files in uploads directory
    Navigate to wp-content/uploads/ and recursively search for .svg files. In WordPress media library, filter by SVG MIME type if available.
    Affected if SVG files exist in the uploads folder that were uploaded by users with Author-level permissions - these could contain malicious scripts.
  4. Inspect SVG files for malicious content
    Open each SVG file in a text editor and look for <script> tags, javascript: URI handlers, onload/onerror event handlers, or foreignObject elements embedding HTML with scripts.
    Affected if Any uploaded SVG contains script tags, javascript: protocols, or event handlers like onload - this indicates active exploitation or pre-existing malicious uploads.

You are affected if the AM LottiePlayer plugin is active, version is below 3.6.0, and users with Author permissions can upload SVG files that may contain embedded scripts.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input sanitization for SVG uploads using an allowlist approach and server-side validation, combined with proper output escaping when rendering SVG content. Upgrade to version 3.6.1 or later if available.

Recommended fix Moderate confidence

Latest version available on wordpress.org (replace 3.6.0)

  1. 1. Log in to the WordPress admin dashboard with an account having Administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the AM LottiePlayer plugin in the list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload the latest version from wordpress.org/plugins/am-lottie-player
  6. 6. After updating, verify the plugin status shows the current version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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