transfer.sh

SECURITY WARNING IP filter and HTTP auth bypass via unauthenticated X-Forwarded-For header spoofing transfer.sh Easy and fast file sharing from the command-line. This code contains the server with everything you need to create your own instance. Transfer.sh currently supports the s3 Amazon S3,...

CVE-2026-100159

The Popup Box plugin for WordPress (versions 6.4.1 to 6.4.2 ) is vulnerable to unauthenticated arbitrary shortcode execution . The root cause is the ays_popup_get_user_ip() function, which reads client-controlled headers (such as Client-IP and X-Forwarded-For) and inadequately sanitizes them usin...

CVE-2026-72815-poc

CVE-2026-72815: go-chi/chi middleware.RealIP IP Spoofing PoC 日本語版 Overview This repository contains a local Proof of Concept PoC for CVE-2026-72815 GHSA-3fxj-6jh8-hvhx, an IP spoofing vulnerability in go-chi/chi's middleware.RealIP. The vulnerable middleware blindly trusts the first leftmost valu...

burpFakeIP

burpFakeIP Download and use: Releases 2021/09/24 1. Fixed a bug reported by M00nBack. 2. Added an AutoXFF switch, and set AutoXFF to disabled by default. If you need the plugin to add a random XFF header to every request, you can select ON in the right-click menu to enable it. 2021/05/21 Refactor...

requests-ip-rotator

Proudly sponsored by Swiftproxy High-performance residential proxies with an 80M+ IP pool across 195+ countries — improve request success rates and reduce IP blocks during large-scale data collection and browser automation. Perfect for use with requests-ip-rotator, Playwright, Selenium, and other...

Silent-Call

Silent;Call Pre-authentication remote root on Cisco Unified Communications Manager 15.x Three HTTP requests. Zero credentials. Root access. Every call is now yours. Kill Chain Step| Component| Description ---|---|--- 1| Spoofhack| X-Forwarded-For header spoofing bypasses localhost restriction on...

CVE-2024-35584

CVE-2024-35584 OpenSIS Authenticated SQL Injection Description There exists a SQL injection vulnerability in Ajax.php, ForWindow.php, ForExport.php, Modules.php, functions/HackingLogFnc.php. This finding affects OpenSis Community Edition 9.1 to 8.0 and possibly versions below. Proof of Concept In...

CVE-2026-110723

In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...

CVE-2026-110724

In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...

CVE-2026-37432

CVE-2026-37432 Location: Apiutil.java: 107-113 Principle: Directly trusting the X-Forwarded-For request header, which can be forged to manipulate IP addresses. Exploitation method: X-Forwarded-For: 127.0.0.1...

Typecho-Multiple-Vulnerabilities

Typecho Multiple Vulnerabilities This repository contains the exploits of the following vulnerabilities: CVE-2024-35538: In Typecho v1.3.0 there is a Client IP Spoofing vulnerability, which allows malicious actors to falsify their IP addresses by specifying an arbitrary IP as value of...

CVE-2026-110726

In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...

CVE-2026-110723

The api-gateway software (versions up to 1.7.3 ) is vulnerable to a rate-limiting bypass because the default ClientIpKeyResolver retrieves the per-client bucket key from the leftmost element of the X-Forwarded-For request header. Since this element is provided by the client and is not validated a...

CVE-2026-110723

In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...

EUVD-2026-102030

In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...

CVE-2026-110724

The api-gateway software (versions up to 1.7.3 ) contains a vulnerability in the default rate-limit key resolver, ClientIpKeyResolver . The component derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header without validating it against a trusted-proxy lis...

EUVD-2026-102029

In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...

CVE-2026-110726

The api-gateway software, in versions up to 1.7.3 , is vulnerable to a rate-limit bypass due to the ClientIpKeyResolver component. The root cause is that the resolver derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header without validating it against a ...

EUVD-2026-102022

In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...

CVE-2026-110726

In api-gateway versions till 1.7.3, The default rate-limit key resolver, ClientIpKeyResolver, derives the per-client bucket key from the leftmost element of the X-Forwarded-For request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy...