Slashdot Mirror
WordPress Now Powers 25% of the Web
An anonymous reader writes: According to data from W3Techs one in four websites is now powered by WordPress. According to the report: "WordPress is used by 58.7% of all the websites whose content management system we know. This is 25.0% of all websites.” Venturebeat reports: "Today is a big day for the free and open-source content management system (CMS). To be perfectly clear, the milestone figure doesn't represent a fraction of all websites that have a CMS: WordPress now powers 25 percent of the Web.
About 95% of the WordPress sites I've run across have allowed user enumeration, exposed internal paths, or had old software that could be exploited. So...I'd probably say that "25% of all websites are WordPress" really means "at least 24% of all websites are insecure".
is nigh. This is a sign
Is this a problem of WordPress, or just a popular CMS? If the admins aren't doing their job for WordPress, why would they start doing it for some other package?
I once took an excursion to Reddit, and later HN. Unlimited up/down voting sucks when dealing with a hive-mind.
According to the linked report, 57.4% of websites aren't using a CMS at all. So Wordpress is a distant second to "None".
#DeleteChrome
What is the actual risk from user enumeration, especially on a site not about a medical condition?
And how can it be prevented? Do you really want to allow two users to have the same username? If a user sends a private message to a nonexistent user, what error message strikes the best balance between security and usability?
I know those made it in there because they were picked up in in the generator meta tag at the site root. That doesn't feel like a great methodology to me, honestly.
It's a shame that ignorant designers and pseudo-developers have tricked so many hapless clients into running WordPress because it's easy. "Easy" here actually means that through a celestial confluence of bad architecture, poor development practice, and sly marketing, a third party market for themes sprang into being, with an horde of add-ons written by neophytes who aspire to writing code only as bad as the WP core, their sole source of PHP practices.
But that's not all. The majority of that monumental-seeming 25% wasn't set up by Joe Hipster for his easily enamored "e-commerce" clients. No, they're deployed via script by phishers and other scammers.
Its ease of use is second to none and that does matter. It also makes sense, sadly, that its plugin repo is now full of freemium. There's clearly a large market but I hope that the genuinely free and quality plugins will remain. Without them, this number wouldn't be.
>> Is this a problem of WordPress, or just a popular CMS?
User enumeration is ON by default in WordPress and it's baked into the design. (There are plug-ins to disable it but most people don't use them.) This is pretty unique among LMSs. WordPress's architecture (which allows the use of old plug-ins) also frequently seems to lead to the reintroduction of helper files that have old vulnerabilities, two of which happen to frequently be "directory browsing" or "internal path disclosure". As for keeping old software up-to-date, that's a problem that all LMS's have to deal with, but there's usually enough on these other WordPress-specific issues on a target site to give your average security person a place to dig in.
Plus, it's a better love story than Twilight!
"WordPress Now Powers 25% of the Web"
Sorry, I ain't buying it. Yes, there are a lot of WordPress sites out there, but 1 in every 4 is a WordPress site?
I call bullshit.
Just cruising through this digital world at 33 1/3 rpm...
And I would rephrase it.......25% of websites are absolutely insecure, and 24% are trivially insecure.* Let's be honest, a fully patched and configured WordPress site just means an attacker has to work a little harder to find a vulnerability.
*Not exclusive....a good portion of the other 75% of websites likely have problems, too.
"First they came for the slanderers and i said nothing."
considering how many wordpress sites are insecure, unpatched and poorly configured I find this news scary not exciting, especially with how readily available exploits for it are.
Because other CMS are complete. Wordpress relies on everything to be a plugin. Upgrade your wordpress, break the plugins your site depends on. Even if they don't break right away, there are lots of small problems that can happen later, or only under certain circumstances. Been there, done that.
Wordpress isn't a CMS for actual people to use. It's a pre-hacked system for people who like tinkering with systems. You want an actual CMS, go elsewhere, and I'm not talking about rival free software platforms.
Shutting down free speech with violence isn't fighting fascism. It IS fascism!
One could arguably call Dreamweaver a "static CMS". It has templates and other do-dads for formatting reuse, and has FTP sync-up management.
Table-ized A.I.
I had no idea there were that many blogs that nobody reads.
Yes, but then you won't get all the "cool" hipsters to work on it. NodeJS has a rocket science mystique about it that attracts pioneers and fools alike. I won't comment on what I really think of the technology, but rather address it as a social phenomenon. Getting work done and being "where it's at" may not be the same thing.
Table-ized A.I.
Wordpress is incredibly easy to set up. I know someone who's computer skills extend to word, excel and a tiny bit of Photoshop who has a domain and wordpress based blog.
With that kind of low barrier to entry it stands to reason that people will have no idea about security. Some people will say the fault is with wordpress but the reality is wordpress can be setup securly and I'm willing to bet that if it were any other CMS we were talking about the results would be the same.
Yes, but then you won't get all the "cool" hipsters to work on it. NodeJS has a rocket science mystique about it that attracts pioneers and fools alike. I won't comment on what I really think of the technology, but rather address it as a social phenomenon
Web programming (maybe more than any other area of programming?) goes through trends where one technology then another is hip and cool. It's like butterflies on crack or something.
I think the reason it happens in web programming especially is because there is no good answer. If you want to do embedded programming, then C/C++ are a good answers. If you want to do corporate software, then Java and C# work decently. But for the web, there's not really a good way to build web pages. HTML/CSS are kind of a pain, with incompatibilities abounding. For Javascript, you have to look for the good parts before you see them. Because they are poor tools, it's easy to create a system that appears to be better (not so easy to build one that is actually better, of course).
"First they came for the slanderers and i said nothing."
So popular, and yet they still haven't fixed the hugely annoying core issue of emulating magic quotes, even years after PHP itself completely threw out the feature.
Every time something becomes too dominant, we should not celebrate, we should worry. Doesn't matter if it's Windows, or IE or Oracle or the iPhone or Apache - we need competition to move and innovate.
In the CMS world, there is fierce competition, fortunately, but there are also high barriers already. A new CMS system will not be used in many commercial projects, no matter the merits, because the customers know a few big ones and if you don't drop their names, your pitch is out.
Almost 60% is quite terrible, especially with a project that has always had serious security issues.
Assorted stuff I do sometimes: Lemuria.org
WordPress is good.
Ok, stop laughing and hear me out.
We all know that with all the shitty web-cmses out there, the ones built on LAMP (PHP) are the oldest that actually have a finished and working feature set.
Show me one non-PHP CMS with the featureset of WP, Joomla, Drupal, EZ Publish or Typo 3, closed source or FOSS. You won't find any.
PHP and the CMSes built with it are at least ten years ahead of the game in the market they were built for - that's a simple fact that no one can deny.
And of those, the mess called WP is actually the best that fits every mold.
- It's primarly a blogging engine - which is what most people want and need anyway. ... and so forth ...
- It takes about 3 clicks and ten seconds to move it away from the blogging perspective to a regular web CMS.
- It's dead simple to install.
- It uses the hook model (also found in Drupal) to implement features that can be applied flexibly. And while that principle is questionable at best - especially from a performance standpoint - there is no doubt that it is *very* easy to use to implement custom features and setups.
- The documentation actually exisits and is pretty good.
- The community is massive. It's basically an army of tinkerers fiddling away at extensions and plugins.
- It has an official full blown mobile management app downloadable for free.
- It has a large, semi-post-capitalistic hip company baking it and it's development. (They all work remote, from around the planet and put their money where their mouths are.)
- There are popular WP plugins built by people who can't programm - but they work (sort of) and are installed/activated/deactivated/uninstalled within seconds.
- The architecture is a bizar convoluted shoddy mess. But you can start tinkering with it within minutes and won't feel bad about it - because, hey, guess what, it's a mess already.
- Modifying templates and themes in a non-destuctive update-safe manner is dead simple.
In an nutshell:
WordPress is PHPs philosophy carried 1on1 into the application/CMS layer.
That is why it's so successful.
And rightfully so.
We suffer more in our imagination than in reality. - Seneca
I have scraped my knuckles badly on drupal versions 6 and 7. I won't ever go near it again, ever. I basically agree with every (comprehensible) thing in your post. Fanboys, facades, false promises and vapourware along wih a bunch of seriously obnoxious contributors and deluded neophytes.
Yeah, it will run a web site. No, it will not run your website.
Wordpress on the other hand is a great money maker for a dev and can be hollowed out and used in any way you like. Highly flexible once understood, just roll your own theme and plugins.
Is this a problem of WordPress, or just a popular CMS?
Drupal is also hugely popular, to the extent that it's actually a government favorite, and yet it doesn't have the same kind of holes as WordPress. That's not to say that it's wholly secure; there's advisories for Drupal all the time. But I think also that a different kind of user installs Drupal, one who actually knows their way around a line of code here and there, and one who will keep up with their updates. Even though WP has automatic updates and Drupal doesn't, WP gets exploited far more... even per capita, AFAICT.
If the admins aren't doing their job for WordPress, why would they start doing it for some other package?
WP is worse by design so the holes are bigger.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
Yeah, it will run a web site. No, it will not run your website.
Having seen all manner of site implemented with Drupal, from 100% flash interfaces for bands and albums and the like backed by its excellent XML-RPC functionality to government websites handling more hits than your mom, I suspect the problem is that it will not run your website. If you're involved, you'll fuck it up.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
As someone who had to dig deep into WordPress codebase at some low point in life... there's little admins can do about it.
Besides, one of the strong selling points of WordPress is its engine for supporting plugins, which is itself a vast ecosystem. In other words, it allows you to run the most terrible pile of code you could ever encounter on the Internet.
sure they are content management systems. they're used to manage content for millions of websites, even for the governments. the content is created, edited and generated from them and in some cases automatically uploaded.. just because they suck doesn't mean that they're not content management systems.
\\"A content management system (CMS)[1][2][3] is a computer application that allows publishing, editing and modifying content, organizing, deleting as well as maintenance from a central interface.[4] Such systems of content management provide procedures to manage workflow in a collaborative environment.[5] These procedures can be manual steps or an automated cascade. CMSs have been available since the late 1990s."
I'd call them CMMS's. Content Mis-Management Systems.
They lack the fundamental feature of the subject matter though, a database back end with a front end script letting the editors or others make changes with a browser. Regardless of whatever website's definition of it, the core of what people mean by "CMS" is a database and a scripting language running things, and a browser to edit.
In that sense, only SharePoint counts and that's a many generations later offshoot used with FrontPage sometimes. DreamWeaver doesn't count. IF those tools are used they are to manage the template on top of the script, and not the scripting, and not the database.
Is this a problem of WordPress, or just a popular CMS? If the admins aren't doing their job for WordPress, why would they start doing it for some other package?
Because for most websites, I've got to pentest from tens of IP addresses to find your vulnerabilities. There is a minimum bar for cracking your site. But if you're running Wordpress I can look at your meta tags and know wxactly which exploits will work and what I will get out of them. Even better, I can use DuckDuckGo to find your site and tens of thousands like it, all with doors wide open.
The difference between Wordpress and a well-built site is the difference between the corner prostitute and Melinda Gates. Somebody will be fucking both of them, but one is available for all to come and do as they please, while the other requires just the right special touch and quite a bit of luck and patience.
It is dangerous to be right when the government is wrong.
Well, not to leave Drupal out too much, it did have https://www.drupal.org/SA-CORE....
Oh yeah, it's deeply embarrassing when your framework intended to stop SQL injection has a SQL injection hole in it. But it's not quite as embarrassing as being a constant source of infection to the rest of the interwebs because you're so supremely easy to exploit as WP. It also got fixed quite promptly...
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
You cannot assume that web sites which don't tell you what CMS they use are either not using one or that 25% of them are using WordPress. All you can conclude is that 25% of Web Sites reporting a CMS use WordPress.
Furthermore, the statistic is meaningless since it doesn't say how much web traffic reaches those sites. It wouldn't surprise me a bit to learn that the vast majority of them are one or two page vanity sites that don't get any traffic at all (other than the occasional bot)
Yes, it is better that your plugins contain the sql-injection attacks so the core doesn't have to deal with them.
The point about the traffic is valid.
But the actually path to the statistic is:
- 57.4% of sites reported no CMS
- 25% of sites reported WordPress
- From the first, 42.6% of sites reported some CMS
- WordPress is 25/42.6 = ~58% of all sites that did report
Total bollocks
If you gave me a choice between a printer and a giraffe with explosive diarrhoea, i'll get my ladder and my raincoat
Just my opinion, but I think the reason for it has a lot to do with the fact that Google changed PageRank to increase visibility of sites that recognize mobile browsers and render accordingly. Getting that to work well is non-trivial, and WordPress makes it easy for the non-technical. For the part of the web where you just want to throw something up and have it render correctly in all browsers and don't want to spend a lot of time on it, you're going to use a CMS like WordPress. I think WordPress is probably going to end up being a vital part of web infrastructure a lot quicker than anyone really expected.
Node.js is about one thing, getting cheap front end developers to do backend programming. It doesn't teach them about databases, algorithms, security or design though. JavaScript is a pain to debug so pushing it into the backend was utter stupidity.
If you look at the code quality of many node modules, you'll cry. JavaScript developers don't understand backward compatibility. Try using a yeoman install sometime and see what I mean.
I am an experienced web developer who has worked with both PHP, ASP, ASP.NET and ASP.NET MVC.
In my opinion PHP is very powerful and I enjoy working with it because of how flexible it is but it has a lot of legacy baggage it must carry for the forseeable future but I don't believe PHP in itself is bad as people paint it but rather it's the inexperienced and the incompetent that give PHP its bad name because they don't write or setup their scripts with security in mind so you end up with all these PHP sites with security holes big enough to fly a 747 jumbo jet through.
Well, I don't consider ASP.NET to be particularly great for web programming either lol
"First they came for the slanderers and i said nothing."
give me user #1
Then we've found the real WTF: sequential assignment of user IDs. Instead of relying on MySQL AUTO_INCREMENT, it should be using random_int(0, 999999999) or the like.
On a system like WordPress, you always tell the user "yep, I just created that account" during user registration but you use the email address already on file for the existing to send an alert to the first registered user saying "hey, someone just tried to recreate your account - was that you"?
Consider the following cases:
In each case, what should be displayed, and what mail should be sent? In the second case, sending mail only to Staisy and not to the attacker would indicate to the attacker that the name staisy is in use. And in the third case, sending mail only to Staisy and not to the image board members would flood her inbox.
Or would it be a better idea to shun usernames entirely, instead relying on the e-mail address as the sole primary key to uniquely identify an author of an article or comment? As far as I can tell, that would imply displaying that e-mail address to the world, including spambots that scrape web sites.
Most WordPress systems I've seen don't use comments
If that's true, that might be what I'm missing. I tend to associate the WordPress brand with blogs that have comment sections.
The problem is that black hats and the NSA also know this and will be concentrating on wordpress vulnerabilities. Any 0-day vulnerability in wordpress would be devastating.
--
Time is on my side
If your CMS requires a competent admin to be secure, it has no business marketing itself as a turnkey solution.
Your ad here. Ask me how!
If you have a billion possible user IDs, but only a thousand correspond to users with commenting privileges and only ten correspond to accounts with anything near administrator-level access, an automated online process will have a heck of a time getting through whatever throttling you've already put in place.
You could call Dreamweaver a polished turd and you'd also be correct.
Well, being a PT and being a static-file CMS are not necessarily mutually exclusive, especially since the CMS field is full of PT's, and Un-PT's.
Table-ized A.I.
So how was she? All the time and patience worth it?
Ask Bill. He always gets the girl!
It is dangerous to be right when the government is wrong.
Everywhere I've seen use WordPress use it like frontpage. If FP isn't a CMS, then neither is WordPress for most uses.
It'd be like buying salesforce.com to use as a shared calendar. It's not bad as a shared calendar. But it's too hard to set up and too expensive for that, so most people who bother to get it would also use the (assumed) CRM functions. But if someone didn't use a single CRM in a CRM, is it still a CRM?
The same thing applies to WP. The smaller company sites I see using it use it because that's what their web admin requires for content generation because it's easier to adminstrate (often farming out the actual web site admin to a 3rd party, while generating content in-house - the old analogy being the in-house would use Front Page, and email the page to the web admin, who would admin the server and upload pages to it).
Stupid, I'd agree. But common, from what I've seen.
Learn to love Alaska
WordPress has just released that they are changing their name to Skynet.
Troll is not a replacement for I disagree.