CVE-2024-25676VulnerabilityPublished 1 May 2024Updated 30 May 2025

CVE-2024-25676: n/a

Source CVE Database V5

Not known to be exploited · CVSS 4.7 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.7Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
npmviewerjs`pkg:npm/viewerjs`Other threats	Affected =0.5.8	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate mitigation involves auditing all web applications and portals for the presence of ViewerJS 0.5.8 or earlier versions. 2. If ViewerJS is in use, restrict or sanitize all user-controllable URL parameters that influence content loading to prevent injection of malicious URLs. 3. Implement Content Security Policy (CSP) headers to restrict the domains from which resources can be loaded, thereby limiting the impact of out-of-band resource loading. 4. Employ URL validation and whitelist approaches to ensure only trusted URLs are processed by the ViewerJS component. 5. Educate users to recognize suspicious redirects and avoid clicking on unexpected links. 6. Monitor web server logs for unusual redirect patterns or external resource requests indicative of exploitation attempts. 7. Engage with the ViewerJS community or maintainers to track the release of official patches or updates addressing this vulnerability and plan prompt upgrades. 8. Where feasible, consider alternative document viewers with stronger security postures until a fix is available. 9. For internal applications, restrict access to trusted networks and implement network segmentation to reduce SSRF impact.

Description

An issue was discovered in ViewerJS 0.5.8. A script from the component loads content via URL TAGs without properly sanitizing it. This leads to both open redirection and out-of-band resource loading.

Impact

For European organizations, the impact of CVE-2024-25676 depends on the extent to which ViewerJS is integrated into their web applications or internal portals. Organizations using ViewerJS to display documents to employees, customers, or partners may inadvertently expose users to phishing risks via open redirects, undermining user trust and potentially leading to credential theft or malware infections. The out-of-band resource loading could be exploited to perform SSRF attacks, which might allow attackers to probe internal networks or exfiltrate data indirectly. Although the vulnerability does not directly compromise confidentiality or availability, the integrity impact and user redirection risks can facilitate broader social engineering or lateral attack chains. Given the medium severity and requirement for user interaction, the threat is moderate but should not be overlooked, especially in sectors with high regulatory requirements such as finance, healthcare, and government. Additionally, organizations with strict data protection obligations under GDPR must consider the reputational and compliance risks associated with phishing or SSRF incidents stemming from this vulnerability.

CWE-601URL Redirection to Untrusted Site ('Open Redirect') (opens in a new tab)
Base weaknessLikelihood of exploit: LowOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
Use an intermediate disclaimer page that provides the user with a clear warning that they are leaving the current site. Implement a long timeout before the redirect occurs, or force the user to click on the link. Be careful to avoid XSS problems (CWE-79) when generating the disclaimer page.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
OWASP Cheat Sheets
Mass Assignment (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V5.1.5 (opens in a new tab)
Attack patterns
Cross-Site Flashing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 16:10 UTC

WeaknessesCWE-601

Technical details

References

Community reviews

Related threats