Skip to main content
VulnerabilityPublished

CVE-2025-55060: Priority Web · Open Redirect

Affects Priority WebSource CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% 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:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Priority WebAffected
  • <=23.0
Fixed in–

AI-suggested

  1. Implement strict validation and sanitization of all user-controlled redirect parameters to ensure only trusted internal URLs are allowed.
  2. Employ allowlists for redirect destinations rather than blacklists to prevent arbitrary external redirects.
  3. Use relative URLs for internal redirects instead of absolute URLs to reduce risk.
  4. Educate users and employees about the risks of phishing and suspicious links, emphasizing caution with unexpected redirects.
  5. Monitor web server logs for unusual redirect patterns or suspicious URL parameters that may indicate exploitation attempts.
  6. Deploy web application firewalls (WAFs) with rules to detect and block open redirect attempts targeting Priority Web.
  7. Coordinate with Priority to obtain and apply security patches promptly once released.
  8. Consider implementing multi-factor authentication (MFA) to reduce the impact of credential theft resulting from phishing.
  9. Review and update incident response plans to include scenarios involving open redirect exploitation and phishing campaigns.
  10. Conduct regular security assessments and penetration tests focusing on URL redirection mechanisms within Priority Web.

Description

CWE-601 URL Redirection to Untrusted Site ('Open Redirect')

References

Community reviews

Loading reviews…