Show filters
17 Total Results
Displaying 1-10 of 17
Sort by:
Attacker Value
Unknown

CVE-2023-49845

Disclosure Date: December 09, 2024 (last updated December 21, 2024)
Missing Authorization vulnerability in Loud Dog Redirects allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Redirects: from n/a through 1.2.1.
0
Attacker Value
Unknown

CVE-2023-47761

Disclosure Date: December 09, 2024 (last updated December 21, 2024)
Missing Authorization vulnerability in WPDeveloper Simple 301 Redirects by BetterLinks allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Simple 301 Redirects by BetterLinks: from n/a through 2.0.7.
0
Attacker Value
Unknown

CVE-2024-28849

Disclosure Date: March 14, 2024 (last updated January 05, 2025)
follow-redirects is an open source, drop-in replacement for Node's `http` and `https` modules that automatically follows redirects. In affected versions follow-redirects only clears authorization header during cross-domain redirect, but keep the proxy-authentication header which contains credentials too. This vulnerability may lead to credentials leak, but has been addressed in version 1.15.6. Users are advised to upgrade. There are no known workarounds for this vulnerability.
0
Attacker Value
Unknown

CVE-2024-1566

Disclosure Date: February 28, 2024 (last updated February 28, 2024)
The Redirects plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the save function in all versions up to, and including, 1.2.1. This makes it possible for unauthenticated attackers to change redirects created with this plugin. This could lead to undesired redirection to phishing sites or malicious web pages.
0
Attacker Value
Unknown

CVE-2023-26159

Disclosure Date: January 02, 2024 (last updated January 10, 2024)
Versions of the package follow-redirects before 1.15.4 are vulnerable to Improper Input Validation due to the improper handling of URLs by the url.parse() function. When new URL() throws an error, it can be manipulated to misinterpret the hostname. An attacker could exploit this weakness to redirect traffic to a malicious site, potentially leading to information disclosure, phishing attacks, or other security breaches.
Attacker Value
Unknown

CVE-2022-0536

Disclosure Date: February 09, 2022 (last updated February 23, 2025)
Improper Removal of Sensitive Information Before Storage or Transfer in NPM follow-redirects prior to 1.14.8.
Attacker Value
Unknown

CVE-2022-0155

Disclosure Date: January 10, 2022 (last updated February 23, 2025)
follow-redirects is vulnerable to Exposure of Private Personal Information to an Unauthorized Actor
Attacker Value
Unknown

CVE-2021-24356

Disclosure Date: June 14, 2021 (last updated February 22, 2025)
In the Simple 301 Redirects by BetterLinks WordPress plugin before 2.0.4, a lack of capability checks and insufficient nonce check on the AJAX action, simple301redirects/admin/activate_plugin, made it possible for authenticated users to activate arbitrary plugins installed on vulnerable sites.
Attacker Value
Unknown

CVE-2021-24355

Disclosure Date: June 14, 2021 (last updated February 22, 2025)
In the Simple 301 Redirects by BetterLinks WordPress plugin before 2.0.4, the lack of capability checks and insufficient nonce check on the AJAX actions, simple301redirects/admin/get_wildcard and simple301redirects/admin/wildcard, made it possible for authenticated users to retrieve and update the wildcard value for redirects.
Attacker Value
Unknown

CVE-2021-24352

Disclosure Date: June 14, 2021 (last updated February 22, 2025)
The export_data function of the Simple 301 Redirects by BetterLinks WordPress plugin before 2.0.4 had no capability or nonce checks making it possible for unauthenticated users to export a site's redirects.