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...

CVE-2014-0195

XML-RPC WordPress Brute-Force Exploit Script This repository contains a Python-based proof of concept PoC for brute-forcing login credentials on WordPress instances vulnerable to CVE-2014-0195, where the XML-RPC system.multicall function can be exploited to attempt multiple login requests in a...

cve-2026-8697

CVE-2026-8697: Login Rate Limit Bypass on TP-Link Archer C64 CVE-2026-8697 is a logic flaw in the TP-Link Archer C64's OS called TPOS in the debug message. It lets any unprivileged user connected to the router to bypass the web UI rate limit by using a residual SSH service. A simple Python script...

CVE-2026-11103-GraphQL-Batching-Alias-Rate-Limit-Bypass

3. CVE-2026-11103 – GraphQL Batching Alias Rate Limit Bypass Program Code Node.js + Python Exploit // graphqlratelimitserver.js - GraphQL with naive rate limiter const express = require'express'; const graphqlHTTP = require'express-graphql'; const buildSchema = require'graphql'; const schema =...

CVE-2016-16113-POC

Get RCE - Bludit CMS Exploit | | / / \ / | | \ \ / / ' | | | | ' | | | | | \ V /| | | | || | | | | | | | ,|/ / || ||/|| || ||| An automated exploitation tool that combines CVE-2019-17240 Authentication Bypass and CVE-2019-16113 Arbitrary File Upload to achieve remote code execution on...

xmlrpc-brute

WordPress XML-RPC Bruteforce Tool A tool designed to test WordPress sites for XML-RPC vulnerabilities by attempting to brute force user credentials through the XML-RPC interface. Description This tool tests WordPress installations for XML-RPC authentication vulnerabilities. It can perform standar...

CVE-2024-25277

CVE-2024-25277 discovered on MW45APT02.0002 Resources and PoCs This repo serves as collection of scripts and PoCs gathered during analysis and discovery of CVE-2024-25277. You can read more about the finding on:...

vaultwarden-ip-header-spoof

abraxaslabs.tech · github.com/abraxas · @abraxasnull · [email protected] · vaultwarden-ip-header-spoof vaultwarden-ip-header-spoof Vaultwarden 1.37.3 - dani-garcia Default IPHEADER=X-Real-IP plus IPHEADERTRUSTEDPROXIES=local treats any non-global TCP peer as a reverse proxy. Stock Docker...

CVE-2021-3138

..| Discourse 2.7.0 - CVE-2021-3138 |.. Description : Rate limit Bypass which leads to 2FA Bypass Tested Version : 2.7.0 Attack Type: Remote Impact : 2FA Bypass Vendor of Product : https://www.discourse.org Additional Information : Discourse is discussion platform built for the next decade of the...

CVE-2024-41276

CVE-2024-41276 Kaiten Authentication Bypass Kaiten - a workflow management system. A vulnerability in Kaiten allows attackers to bypass the PIN code authentication mechanism. The application requires users to input a 6-digit PIN code sent to their email for authorization after entering their logi...

CVE-2026-111934

Coder before 2.34.7 contains an IP spoofing vulnerability in the ExtractRealIPAddress middleware that trusts the leftmost, client-supplied X-Forwarded-For value instead of the client IP appended by a reverse proxy. Attackers can send forged X-Forwarded-For values through appending proxies to bypa...

EUVD-2026-103301

Coder before 2.34.7 contains an IP spoofing vulnerability in the ExtractRealIPAddress middleware that trusts the leftmost, client-supplied X-Forwarded-For value instead of the client IP appended by a reverse proxy. Attackers can send forged X-Forwarded-For values through appending proxies to bypa...

CVE-2026-111934 Coder before 2.34.7 IP Spoofing via X-Forwarded-For Header

Coder before 2.34.7 contains an IP spoofing vulnerability in the ExtractRealIPAddress middleware that trusts the leftmost, client-supplied X-Forwarded-For value instead of the client IP appended by a reverse proxy. Attackers can send forged X-Forwarded-For values through appending proxies to bypa...

PT-2026-116502

Name of the Vulnerable Software and Affected Versions Coder versions prior to 2.34.7 Description An IP spoofing issue exists in the ExtractRealIPAddress middleware. The system incorrectly trusts the leftmost value provided by the client in the X-Forwarded-For header rather than the client IP...

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-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

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...

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...