90,000 WordPress Sites Affected by Arbitrary File Upload and Authentication Bypass Vulnerabilities in Jupiter X Core WordPress Plugin

On August 6th, 2024, Wordfence received a submission for an Arbitrary File Upload vulnerability in Jupiter X Core, a WordPress plugin with more than 90,000 active installations. This vulnerability makes it possible for an unauthenticated attacker to upload arbitrary files to a vulnerable site and achieve remote code execution, which is typically leveraged for a complete site takeover.

On the same day, we also received a submission for a Limited Authentication Bypass to Account Takeover vulnerability in the same plugin. This vulnerability makes it possible for unauthenticated attackers to log in as the first user who logged in using Google or Facebook, including administrator accounts.

Props to Geo Void who discovered and responsibly reported these vulnerabilities through the Wordfence Bug Bounty Program. This researcher earned a bounty of $2,145.00 for the Arbitrary File Upload and $1,690.00 for the Authentication Bypass to Account Takeover discoveries.

All Wordfence customers, as well as those using the free version of our plugin, are protected against any exploits targeting the Arbitrary File Upload vulnerability by the Wordfence firewall’s built-in Malicious File Upload protection.

Paid Wordfence users received a firewall rule to protect against any exploits targeting the Authentication Bypass to Account Takeover vulnerability on August 14, 2024. Sites using the free version of Wordfence received the same protection 30 days later on September 13, 2024.

Wordfence contacted the Artbees team on August 14, 2024, and received a response on August 20, 2024. After providing full disclosure details, the developer released the first patch on August 22, 2024, the second patch on September 12, 2024, and the third patch on September 18, 2024. We would like to commend the Artbees team for their prompt response and timely patch.

We urge users to update their sites with the latest patched version of Jupiter X Core, which is version 4.7.8, as soon as possible.

Source and more details: https://www.wordfence.com/blog/2024/09/90000-wordpress-sites-affected-by-arbitrary-file-upload-and-authentication-bypass-vulnerabilities-in-jupiter-x-core-wordpress-plugin

20,000 WordPress Sites Affected by Privilege Escalation Vulnerability in WCFM – WooCommerce Frontend Manager WordPress Plugin

On August 28th, 2024, Wordfence received a submission for a Privilege Escalation via Account Takeover vulnerability in WCFM – WooCommerce Frontend Manager, a WordPress plugin with more than 20,000 active installations. This vulnerability makes it possible for an authenticated attacker to change the email of any user, including an administrator, which allows them to reset the password and take over the account and website.

Props to wesley (wcraft) who discovered and responsibly reported this vulnerability through the Wordfence Bug Bounty Program. This researcher earned a bounty of $1,127.00 for this discovery.

Paid Wordfence users received a firewall rule to protect against any exploits targeting this vulnerability on August 28, 2024. Sites using the free version of Wordfence will receive the same protection 30 days later on September 27, 2024.

Wordfence contacted the WCLovers team on August 28, 2024, and received a response on the same day. After providing full disclosure details, the developer released a patch on September 23, 2024. We would like to commend the WCLovers team for their prompt response and timely patch.

We urge users to update their sites with the latest patched version of WCFM – WooCommerce Frontend Manager, which is version 6.7.13, as soon as possible.

Source and more details: https://www.wordfence.com/blog/2024/09/20000-wordpress-sites-affected-by-privilege-escalation-vulnerability-in-wcfm-woocommerce-frontend-manager-wordpress-plugin

WP Engine is not WordPress

By Matt Mullenweg in Community, WordCamp

It has to be said and repeated: WP Engine is not WordPress. My own mother was confused and thought WP Engine was an official thing. Their branding, marketing, advertising, and entire promise to customers is that they’re giving you WordPress, but they’re not. And they’re profiting off of the confusion. WP Engine needs a trademark license to continue their business.

I spoke yesterday at WordCamp about how Lee Wittlinger at Silver Lake, a private equity firm with $102B assets under management, can hollow out an open source community. (To summarize, they do about half a billion in revenue on top of WordPress and contribute back 40 hours a week, Automattic is a similar size and contributes back 3,915 hours a week.) Today, I would like to offer a specific, technical example of how they break the trust and sanctity of our software’s promise to users to save themselves money so they can extract more profits from you.

WordPress is a content management system, and the content is sacred. Every change you make to every page, every post, is tracked in a revision system, just like the Wikipedia. This means if you make a mistake, you can always undo it. It also means if you’re trying to figure out why something is on a page, you can see precisely the history and edits that led to it. These revisions are stored in our database.

This is very important, it’s at the core of the user promise of protecting your data, and it’s why WordPress is architected and designed to never lose anything.

WP Engine turns this off. They disable revisions because it costs them more money to store the history of the changes in the database, and they don’t want to spend that to protect your content. It strikes to the very heart of what WordPress does, and they shatter it, the integrity of your content. If you make a mistake, you have no way to get your content back, breaking the core promise of what WordPress does, which is manage and protect your content.

Here is a screenshot of their support page saying they disable this across their 1.5 million WordPress installs.

They say it’s slowing down your site, but what they mean is they want to avoid paying to store that data. We tested revisions on all of the recommended hosts on WordPress.org, and none disabled revisions by default. Why is WP Engine the only one that does? They are strip-mining the WordPress ecosystem, giving our users a crappier experience so they can make more money.

What WP Engine gives you is not WordPress, it’s something that they’ve chopped up, hacked, butchered to look like WordPress, but actually they’re giving you a cheap knock-off and charging you more for it.

This is one of the many reasons they are a cancer to WordPress, and it’s important to remember that unchecked, cancer will spread. WP Engine is setting a poor standard that others may look at and think is ok to replicate. We must set a higher standard to ensure WordPress is here for the next 100 years.

If you are a customer of “WordPress Engine,” you should contact their support immediately to at least get the 3 revisions they allow turned on so you don’t accidentally lose something important. Ideally, they should go to unlimited. Remember that you, the customer, hold the power; they are nothing without the money you give them. And as you vote with your dollars, consider literally any other WordPress host as WP Engine is the only one we’ve found that completely disables revisions by default.

Source: https://wordpress.org/news/2024/09/wp-engine

See also: https://techcrunch.com/2024/09/29/wordpress-vs-wp-engine-drama-explained/

Criminals Keep Hacking Themselves, Letting Researchers Unmask Them

Infostealer malware is often hidden in pirated or cracked software, and hackers then post the harvested credentials and other data online. Criminals have been infected too.

Cybersecurity researchers are increasingly unmasking or finding new information on suspected criminals from a rich and unlikely source: the tsunami of compromised credentials, browser profiles, and other system information available on Telegram. In other words, criminals are accidentally hacking themselves, perhaps by downloading cracked software laden with malware, which is then exposing their identities to researchers, and potentially law enforcement too.

In the latest example, cybersecurity firm Hudson Rock said last week it had uncovered information on Mujtaba Raza and Mohsin Raza, two alleged fraudsters on the FBI’s Most Wanted list. In April 2021, U.S. authorities charged the two men with conspiracy to produce and transfer in false identification documents, three counts of transferring false identification documents, false use of a passport, and aggravated identity theft. The men allegedly ran an illegal e-commerce business out of Karachi, Pakistan, called SecondEye Solution. This company sold digital images of fake passports, driver’s licenses, and national identity cards for more than 200 countries and territories, and the men advertised the company’s services on at least one hacker forum, according to the DOJ’s press release at the time. The DOJ said that a member of the Internet Research Agency LLC, the Russian social media and election interference organization, bought multiple fake identity documents from SecondEye.

Since those charges, Mujtaba and Mohsin have been fugitives.

Now using data from infostealers, which are a class of malware that harvest credentials and other data from an infected computer, Hudson Rock said it had identified two computers that it believes contained data related to the pair. Various pieces of infostealer malware exist, with names such as RedLine, Raccoon, Mars, BlackGuard, and Erbium. These are spread to victims by fake ExpressVPN applications, cryptocurrency wallets, or cracked or pirated software. Once the malware administrators have harvested credentials, they often sell them to other cybercriminals before posting them for free on Telegram. It’s typically here that researchers can collect the exposed credentials and then warn impacted companies. 

Included in the infostealer logs Hudson Rock found were credentials for SecondEye email accounts; cloud storage accounts linked to the same email addresses; and others for Forwarderz, another associated company.

The data harvested by the infostealers and then reviewed by Hudson Rock included much more than just passwords stored on the computers, though. Hudson Rock says it included the “entire browsing history” from one of the machines; auto-fill data, such as addresses, account numbers, and passport numbers; as well as information on when the computer was hacked, its name, and its related IP address. When one of the computers was initially infected, the malware took a screenshot. It shows a Forwarderz-branded Skype account being used, according to Hudson Rock.

Hudson Rock believes the two compromised computers don’t belong to Mujtaba and Mohsin themselves, but two other associates. Facebook and Github profiles linked to the machines, as well as a physical address included in the data, pointed to two men called Muhammad Qamber and Bakhtawar Abbas. Neither man responded to a request for comment from 404 Media.

Infostealer credentials are responsible for the recent wave of Snowflake breaches, in which hackers accessed data from a series of high profile companies, including AT&T and Ticketmaster.

Hudson Rock’s blog post says it was “reviewed and approved by the Federal Bureau of Investigation (FBI), meeting all necessary guidelines for public disclosure.” The FBI did not respond to a request for comment. Neither did Hudson Rock.

In another case, in July researchers from cybersecurity firm RecordedFuture said they found 3,324 unique credentials used to access known child abuse imagery (CSAM) websites. That data also included those peoples’ usernames, IP addresses, and system information, which could let the researchers or law enforcement unmask the users’ real identities.

RecordedFuture said it “used the data contained in infostealer logs and open-source intelligence (OSINT) to identify two individuals and found further digital artifacts, including cryptocurrency addresses, belonging to a third individual.” RecordedFuture did not respond to a request for comment. 

Whether such information would be admissible in court is a separate question, however, and would in part depend on whether law enforcement consider credentials harvested from infostealer infections to be publicly available information. The FBI did not respond to a request for comment.

Source: https://www.404media.co/criminals-keep-hacking-themselves-letting-researchers-unmask-them/

WordPress 6.6.2 Maintenance Release

WordPress 6.6.2 is now installed on most of our client’s sites.

This minor release includes 15 bug fixes in Core and 11 in the Block Editor, addressing issues like unexpected CSS specificity changes in certain themes. For a full summary of the maintenance updates, you can refer to the Release Candidate announcement.

WordPress 6.6.2 is a short-cycle release. The next major release will be version 6.7 planned for November 12, 2024.

Source: https://wordpress.org/news/2024/09/wordpress-6-6-2-maintenance-release/

WordPress TI WooCommerce Wishlist Plugin <= 2.8.2 is vulnerable to SQL Injection

This vulnerability is highly dangerous and expected to become mass exploited.


SQL Injection

This could allow a malicious actor to directly interact with your database, including but not limited to stealing information.

There is no official patch as of September 10, 2024.

Patchstack has issued a virtual patch to mitigate this issue by blocking any attacks until an official fix becomes available, can be tested and be safely applied.

Source and more info: https://patchstack.com/database/vulnerability/ti-woocommerce-wishlist/wordpress-ti-woocommerce-wishlist-plugin-2-8-2-sql-injection-vulnerability

Over 40,000 WordPress Sites Affected by Privilege Escalation Vulnerability Patched in Post Grid and Gutenberg Blocks Plugin

On August 14th, 2024, the Wordfence team received a submission for a Privilege Escalation vulnerability in Post Grid and Gutenberg Blocks, a WordPress plugin with over 40,000 active installations. This vulnerability can be leveraged by attackers with minimal authenticated access to set their role to administrator utilizing the form submission functionality.

Props to wesley (wcraft) who discovered and responsibly reported this vulnerability through the Wordfence Bug Bounty Program. This researcher earned a bounty of $1,127.00 for this discovery. 

Paid Wordfence users received a custom firewall rule to provide protection against any exploits targeting this vulnerability on August 28th, 2024. Wordfence free users will receive the same protection 30 days later on September 27th, 2024.

The Wordfence team sent the full disclosure details to the plugin’s author on August 28th, 2024 and, while they didn’t acknowledge the report immediately, they released a patch just a week after our disclosure on September 5th, 2024. We commend the team at PickPlugins for the quick remediation of this vulnerability.

We urge site owners running a vulnerable version to update their sites with the latest patched version of Post Grid and Gutenberg Blocks, version 2.2.91 at the time of this writing, as soon as possible.

Source and more details: https://www.wordfence.com/blog/2024/09/over-40000-wordpress-sites-affected-by-privilege-escalation-vulnerability-patched-in-post-grid-and-gutenberg-blocks-plugin

Critical Arbitrary File Deletion Vulnerability in MP3 Audio Player WordPress Plugin Affects Over 20,000 Sites

On August 4th, 2024, the Wordfence team received a submission for an Arbitrary File Deletion vulnerability in MP3 Audio Player – Music Player, Podcast Player & Radio by Sonaar, a WordPress plugin with over 20,000 active installations. This vulnerability can be leveraged by attackers to delete critical files like wp-config.php which can lead to remote code execution by authenticated attackers with minimal permissions such as subscribers.

Props to Arkadiusz Hydzik who discovered and responsibly reported this vulnerability through the Wordfence Bug Bounty Program. This researcher earned a bounty of $705.00 for this discovery.

All Wordfence users, including Wordfence Free, and all paid Wordfence users are protected by the Wordfence Firewall’s built-in directory traversal and local file inclusion rules.

Wordfence sent the full disclosure details to the plugin’s author on August 16th, 2024 and they acknowledged the report the same day. The patch was released just over a week later on August 27th, 2024. We commend the team at Sonaar for the quick response and remediation of this vulnerability.

We urge users to update their sites with the latest patched version of MP3 Audio Player – Music Player, Podcast Player & Radio by Sonaar, version 5.7.1 at the time of this writing, as soon as possible.

20,000 WordPress Sites Affected by Remote Code Execution Vulnerability in Bit File Manager WordPress Plugin

On July 24th, 2024, the WordFence team received a submission for a Remote Code Execution via Race Condition vulnerability in Bit File Manager, a WordPress plugin with more than 20,000 active installations. This vulnerability can be leveraged to execute code remotely.

Props to TANG Cheuk Hei (siunam) who discovered and responsibly reported this vulnerability through the Wordfence Bug Bounty Program. This researcher earned a bounty of $358.00 for this discovery.

Paid WordFence users received a firewall rule to protect against any exploits targeting this vulnerability on August 9, 2024. Sites using the free version of Wordfence will receive the same protection 30 days later on September 8, 2024.

We provided full disclosure details to the Bit Apps team on August 14, 2024. The developer released a patch on August 21, 2024. We would like to commend the Bit Apps team for their prompt response and timely patch.

We urge users to update their sites with the latest patched version of Bit File Manager, version 6.5.6 at the time of this writing, as soon as possible.

Source and more details: https://www.wordfence.com/blog/2024/09/20000-wordpress-sites-affected-by-remote-code-execution-vulnerability-in-bit-file-manager-wordpress-plugin

6,000 WordPress Sites Affected by Unauthenticated Critical Vulnerability in WP Job Portal WordPress Plugin

On August 7th, 2024, the Wordfence team received a submission for an unauthenticated Local File Inclusion, Arbitrary Settings Update, and User Creation vulnerability in WP Job Portal, a WordPress plugin with more than 6,000 active installations. This vulnerability can be leveraged to create malicious administrator users, and also can be leveraged to include and execute arbitrary files on the server, allowing for the execution of any PHP code in those files.

Props to Connor Billings who discovered and responsibly reported this vulnerability through the Wordfence Bug Bounty Program. This researcher earned a bounty of $813.00 for this discovery.

Paid Wordfence users received a firewall rule to protect against any exploits targeting this vulnerability on August 19, 2024. Sites using the free version of Wordfence will receive the same protection 30 days later on September 18, 2024.

Wordfence contacted the WP Job Portal team on August 19, 2024, and received a response on the next day. After providing full disclosure details, the developer released the patch on August 21. We would like to commend the WP Job Portal team for their prompt response and timely patch.

We urge users to update their sites with the latest patched version of WP Job Portal, version 2.1.7 at the time of this writing, as soon as possible.

Source and more details: https://www.wordfence.com/blog/2024/09/6000-wordpress-sites-affected-by-unauthenticated-critical-vulnerability-in-wp-job-portal-wordpress-plugin