No, rails-3.2.11 has fixed this vulnerability.