DISQUS

podz · 3 years ago

I'm curious - why post the actual exploit?
Is it to prove it's existence?

Aaron Brazell · 3 years ago

Hey podz-

Most people tend to think, "Aww, a hack will never happen to me". The point of this exercise was to demonstrate how very simple it is. Maybe demonstration will cause folks to be cautious regarding plugins they use.

podz · 3 years ago

But I could now google enough to find that plugin and hit those sites in a couple of clicks.
Surely just saying what you have and omitting the actual exploit would be the way to go?

Darren McLaughlin · 3 years ago

These plugins can be very dangerous. I think the Wordpress culture is to install as many plugins as possible without doing a ton of research.

This one is a very insidious exploit.

Jeremy Wright · 3 years ago

pods: posting the exploit is standard practice, whether it's Microsoft or Apache.

Aaron Brazell · 3 years ago

Sure. And you could also subscribe to bugtraq and find this same kind of information numerous times a day. Secrecy is not always the best policy. I don't make a habit of reporting exploits but I read blogs everyday that do. It's quite the same thing.

Duncan · 3 years ago

No link love for the person who actually discovered it? :-)

Aaron Brazell · 3 years ago

Sure, over here. ;)

drmike · 3 years ago

Podz: Don't forget all those people over on the wp.com forums who keep saying that javascripts, embed, and object tags are safe as well. :)

podz · 3 years ago

drmike - I wasn't saying they were safe. I'm talking about people who can code saying that other code is unsafe.

I've a challenge. If it will be accepted.

Leroy Brown · 3 years ago

It's a shame that it always takes the public posting of the exploit for the author to fix the problem. Although I can't be too hard on someone who creates a plugin at no cost, so I don't know. Mixed feelings as usual.
Can you hold the author liable for any problems, even though his software is free? I'm not sure that it's fair to do so.

Aaron Brazell · 3 years ago

Leroy: Technically, no you can't hold an author liable. In reality though, he's liable. That's how anyone who would get exploited would feel. That's how I would feel if I was hacked as a result. Fortunately, I was able to post the exploit with a link to a new version, so I'd like to think that I worked with Andrew to find a solution before it blew up.

Leroy Brown · 3 years ago

Aaron,
I may feel differently if one of my sites had been hacked - that'll certainly give you a different perspective on the matter. Either way, it's necessary to post the expoit so that a fix can be produced, whether by the author or someone else. Good to see that the author did come up with a fix, so that people had a solution instead of a freak-out period of waiting.

MustLive · 3 years ago

Aaron. As I wrote at my site http://websecurity.com.ua/187/ two weeks ago, I was found a vulnerability in Subscribe To Comments WordPress plugin (and already released the path and plugin developer also worked on next version of plugin). So there are many other cases (among WordPress plugins) with plugin's vulnerabilities, not only in Democracy plugin. And as I see, you also use Subscribe To Comments at your site, so you need to draw attention to this information (and check your plugin).

MustLive · 3 years ago

Aaron. You have already validated my message and then I retrieved my "key" (it need for your version of wp-subscription-manager.php). And after looking to one of the vulnerable scripts (in this case - wp-subscription-manager.php), I can tell you that your site is vulnerable (via Subscribe To Comments plugin)!

You need to update plugin. You can take Subscribe To Comments 2.0.5 from my MustLive Security Pack v.1.0.4 or download last version (Subscribe To Comments 2.0.8) from developer's site.