How severe is CVE-2025-48447?

No CVSS score has been assigned to CVE-2025-48447 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-48447?

CVE-2025-48447 affects the following packages: drupal/lightgallery (Packagist:https://packages.drupal.org/8). Ecosystems affected: Packagist:https://packages.drupal.org/8.

How do I fix CVE-2025-48447?

Update drupal/lightgallery to 1.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-48447 is resolved across your whole dependency graph.

How do I detect CVE-2025-48447 in my Packagist:https://packages.drupal.org/8 dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/lightgallery, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-48447 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2025-48447 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-48447 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-48447?

CVE-2025-48447 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 27th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-48447?

CVE-2025-48447 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2025-48447 published, and has it been updated?

CVE-2025-48447 was published on May 21, 2025 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Packagist:https://packages.drupal.org/8

Not in CISA KEV

CVE-2025-48447 — lightgallery

CVE-2025-48447 is a Cross-site Scripting (XSS) vulnerability in drupal/lightgallery. A fix is available for drupal/lightgallery — see the affected versions and patch details below.

Also known asGHSA-w5px-5878-m9x4

Published

May 21, 2025

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-48447.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs27th percentile — riskier than 27% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

📦drupal/lightgallery

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist:https://packages.drupal.org/8 packages — download data is not available via public APIs for these ecosystems.

Description

This module integrates Drupal with LightGallery, enabling the use of the LightGallery library with any image field or view.

The module does not adequately sanitize user input in the image field’s "alt" attribute, potentially allowing cross-site scripting (XSS) attacks when tags or scripts are inserted.

This vulnerability is partially mitigated by the requirement that an attacker must have permission to create content containing an image field configured to use the LightGallery format.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Packagist:https://packages.drupal.org/8	`drupal/lightgallery`	all versions	1.6.0

Affected Products

1 product · 1 configurations

Application

lightgallerylightgallery_project

< 1.6.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/lightgallery, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update drupal/lightgallery to 1.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-48447 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

This module integrates Drupal with LightGallery, enabling the use of the LightGallery library with any image field or view. The module does not adequately sanitize user input in the image field’s "alt" attribute, potentially allowing cross-site scripting (XSS) attacks when tags or scripts are inserted. This vulnerability is partially mitigated by the requirement that an attacker must have permission to create content containing an image field configured to use the LightGallery format.

O3 Security · Impact-Aware SCA

Is CVE-2025-48447 in your dependencies?

Find it across Packagist:https://packages.drupal.org/8, including transitive dependencies.

Scan my dependencies How O3 SCA works