lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Fri, 12 Mar 2021 14:16:05 +0100
From: jvoisin <>
Subject: Re: [FD] Data Manipulation with X-Forwarded-For header at WordPress

> -------------------------
> "X-Forwarded-For" is a HTTP header used to carry the client's original
> IP address. However, because these headers may very well be added by
> the client to the requests, if the systems/devices use IP addresses
> which decelerate at X-Forwarded-For header instead of original IP,
> various issues may be faced. If the data originating from these fields
> is trusted by the application developers and processed, any
> authorization checks originating IP address logging could be
> manipulated.
I'm not sure I understand what's going on here: The "vulnerability" is 
that "X-Forwarded-For" can be manipulated by the client?

> -------------------------
> Affected Component: Wordpress core
> Affected version Wordpress 5.1
> -Add X-Forwarded-For header to the /wp-admin
> -You will get an error about your IP
> -Next go /wp-admin/admin-ajax.php and add X-Forwarded-For header again
This doesn't make any sense.

There is nothing on Wordpress' website ( ) about an issue like this 
one, nor on the mitre's website ( ).

Can you please elaborate on this issue?

Sent through the Full Disclosure mailing list
Web Archives & RSS:

Powered by blists - more mailing lists