The Wordfence Threat Intelligence Team recently disclosed several Reflected Cross-Site Scripting vulnerabilities that we discovered in three different plugins – Watu Quiz (installed on 5,000 sites), GN-Publisher (installed on 40,000 sites), and Japanized For WooCommerce (installed on 10,000 sites). As with all Reflected Cross-Site Scripting vulnerabilities, these could be leveraged for a complete site takeover as long as an unauthenticated attacker could successfully trick a site administrator into performing an action, such as clicking on a link or visiting a website under the attacker’s control.

All Wordfence customers, including Wordfence Premium, Wordfence Care, and Wordfence Response customers as well as those still using the free version of our plugin, are protected against any exploits targeting these vulnerabilities by the Wordfence firewall’s built-in Cross-Site Scripting protection.

Vulnerability Summaries

---

---

---

Vulnerability Details

Watu Quiz is a plugin that offers site owners the ability to create exams, quizzes and surveys. It allows administrators to review quiz submissions and filter search results by username, email, date taken and quiz score. Unfortunately, the search terms – provided as URL parameters – were not properly sanitized before being echoed on the search form.

Visiting a URL containing a malicious payload sufficed to trigger the execution of malicious JavaScript code in the context of the visiting user’s session. Since the exploitable page was an administrative page, this code could be used to create new administrator users or to perform other similarly severe actions potentially resulting in site takeover.

A vulnerable line of code in the plugin used the user-provided parameter and output it directly:

<input name="dn" type="text" value="<?php echo @$_GET['dn']?>" />

The dn parameter can be used to close out the value attribute, add an onmouseover event (or an onfocus event combined with the autofocus attribute) and execute JavaScript in the context of the victim’s browser.

/wp-admin/admin.php?page=watu_takings&exam_id=1&dn="%2Fonmouseover%3Dalert(123)%2F%2F

Versions up to 3.3.9 of this plugin are vulnerable. The issue is fixed in version 3.3.9.1 as of March 3, 2023.

---

GN Publisher is a plugin that makes RSS feeds which comply with Google News RSS feed technical requirements – necessary for inclusion in the Google News Publisher Center. The plugin addresses some common RSS compatibility issues publishers typically experience.

On its main configuration page It offers a tabbed form where administrators can change plugin-specific settings. However, the plugin does not properly escape the tab name before outputting it.

The software features a button in the top right corner that offers an upgrade to the PRO version. The code for the button in the vulnerable version is shown below (slightly reformatted for legibility):

As can be seen, the button element contains a php echo statement that outputs the tab parameter as a button class attribute. An unauthenticated attacker can take advantage of this and inject attribute-based JavaScript that executes on an event of the attacker’s choosing such as onmouseover, or onfocus in combination with autofocus, assuming they can also successfully trick a site administrator into performing an action.

/wp-admin/options-general.php?page=gn-publisher-settings&tab=hans%22%2F+onmouseover%3Dalert%281%29%3B%2F%2F

Versions up to, and including, 1.5.5 are vulnerable. Version 1.5.6 addressed this issue and was released on February 24, 2023.

---

The plugin Japanized for WooCommerce adds additional features to WooCommerce that make it more user-friendly for a Japanese audience, such as honorific titles and custom payment options geared towards the Japanese market. Similarly to the other two plugins discussed above, Japanized for WooCommerce outputs unsanitized user input provided via URL parameter.

As long as a tab parameter is provided, it will be output as part of the provided JavaScript that follows. A malicious piece of code can be used to close the script tag, open a new one, and include code to be executed on behalf of the visiting user.

/wp-admin/admin.php?page=wc4jp-options&tab=hans%27%3C%2Fscript%3E%3Cscript%3Ealert%281%29%3C%2Fscript%3E

Just like the other two vulnerabilities discussed above, this vulnerability can be exploited by unauthenticated attackers as long as an administrator of a vulnerable site can be tricked into performing an action such as clicking on a link leading them to the vulnerable form.

This issue is patched as of version 2.5.6, which was released on February 28, 2023.

As a final reminder, as is typical for Reflected Cross-Site Scripting vulnerabilities, these attacks can be carried out by unauthenticated users. However, the interaction of a site user is a requirement. Furthermore, the malicious injection does not persist as it is not stored in the database.

Conclusion

In today’s post, we detailed flaws in three plugins that made it possible for attackers to inject malicious JavaScript into a vulnerable site. While the exploitation of these vulnerabilities requires some degree of social engineering, they all could be used for site takeover.

All Wordfence users, including those running Wordfence Premium, Wordfence Care, and Wordfence Response, as well as sites still running the free version of Wordfence, are fully protected against this vulnerability.

If you believe your site has been compromised as a result of these vulnerabilities or any other vulnerability, we offer Incident Response services via Wordfence Care. If you need your site cleaned immediately, Wordfence Response offers the same service with 24/7/365 availability and a 1-hour response time. Both these products include hands-on support in case you need further assistance.

If you have any friends or colleagues who are using one of these plugins, please share this announcement with them and encourage them to update to the latest version as soon as possible.

If you are a security researcher, you can responsibly disclose your finds to us and obtain a CVE ID and get your name on the Wordfence Intelligence leaderboard.

The post Multiple Reflected Cross-Site Scripting Vulnerabilities in Three WordPress Plugins Patched appeared first on Wordfence.

Last week, there were 60 vulnerabilities disclosed in 40 WordPress Plugins and 1 WordPress theme that have been added to the Wordfence Intelligence Vulnerability Database, and there were 16 Vulnerability Researchers that contributed to WordPress Security last week. Review those vulnerabilities in this report now to ensure your site is not affected.

Our mission with Wordfence Intelligence is to make valuable vulnerability information easily accessible to everyone, like the WordPress community, so individuals and organizations alike can utilize that data to make the internet more secure. That is why the Wordfence Intelligence user interface and vulnerability API are completely free to access and utilize both personally and commercially, and why we are running this weekly vulnerability report.

Click here to sign-up for our mailing list to receive weekly vulnerability reports like this and important WordPress Security reports in your inbox the moment they are published.

---

New Firewall Rules Deployed Last Week

The Wordfence Threat Intelligence Team reviews each vulnerability to determine impact and severity, along with assessing the likelihood of exploitation, to verify that the Wordfence Firewall provides sufficient protection.

The team rolled out enhanced protection via firewall rules for the following vulnerabilities in real-time to our Premium, Care, and Response customers last week:

• Paytium <= 4.3.7 – Missing Authorization
• Yoast SEO <= 20.2 – Authenticated (Contributor+) Stored Cross-Site Scripting
• Slimstat Analytics <= 4.9.3.2 – Authenticated (Subscriber+) SQL Injection via Shortcode
• Paid Memberships Pro <= 2.9.11 – Authenticated (Subscriber+) SQL Injection via Shortcodes

Wordfence Premium, Care, and Response customers received this protection immediately, while users still running the free version of Wordfence will receive this enhanced protection after a 30 day delay.

---

Total Unpatched & Patched Vulnerabilities Last Week

Patch Status	Number of Vulnerabilities
Unpatched	3
Patched	57

---

Total Vulnerabilities by CVSS Severity Last Week

Severity Rating	Number of Vulnerabilities
Low Severity	0
Medium Severity	53
High Severity	6
Critical Severity	1

---

Total Vulnerabilities by CWE Type Last Week

Vulnerability Type by CWE	Number of Vulnerabilities
Cross-Site Request Forgery (CSRF)	24
Missing Authorization	17
Improper Neutralization of Input During Web Page Generation (‘Cross-site Scripting’)	9
Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’)	2
Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’)	1
Server-Side Request Forgery (SSRF)	1
Incorrect Privilege Assignment	1
Improper Neutralization of Special Elements in Output Used by a Downstream Component (‘Injection’)	1
Reliance on Untrusted Inputs in a Security Decision	1
Improper Authorization	1
Deserialization of Untrusted Data	1
Information Exposure	1

---

Researchers That Contributed to WordPress Security Last Week

Researcher Name	Number of Vulnerabilities
Marco Wotschka (Wordfence Vulnerability Researcher)	15
Mika	5
Erwan LR	3
Rafshanzani Suhada	3
Rafie Muhammad	2
yuyudhn	2
Nguyen Xuan Chien	1
Nicholas Ferreira	1
Lana Codes	1
FearZzZz	1
Rio Darmawan	1
Omar Badran	1
thiennv	1
Daniel Ruf	1
Alex Sanford	1
Abdi Pranata	1

 

Are you a security researcher who would like to be featured in our weekly vulnerability report? You can responsibly disclose your WordPress vulnerability discoveries to us and obtain a CVE ID through this form. Responsibly disclosing your vulnerability discoveries to us will also get your name added on the Wordfence Intelligence leaderboard along with being mentioned in our weekly vulnerability report.

---

Vulnerability Details

LeadSnap <= 1.23 – Unauthenticated PHP Object Injection via AJAX

---

Multiple E-plugins (Various Versions) – Authenticated (Subscriber+) Privilege Escalation

---

WP Dark Mode <= 4.0.7 – Authenticated (Subscriber+) Local File Inclusion via ‘style’

---

GiveWP <= 2.25.1 – Unauthenticated CSV Injection

---

WP Statistics <= 13.2.16 – Authenticated (Admin+) SQL Injection

---

Paytium: Mollie payment forms & donations <= 4.3.7 – Missing Authorization in ‘create_mollie_account’

---

Paytium: Mollie payment forms & donations <= 4.3.7 – Missing Authorization in ‘create_mollie_profile’

---

Complianz – GDPR/CCPA Cookie Consent <= 6.4.1 – Authenticated (Contributor+) Stored Cross-Site Scripting

---

Weaver Xtreme Theme Support <= 5.0.2 – Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode

---

Cookie Notice & Compliance for GDPR / CCPA <= 2.4.6 – Authenticated (Contributor+) Stored Cross-Site Scripting via ‘cookies_revoke_shortcode’ Shortcode

---

Daily Prayer Time <= 2023.03.08 – Authenticated (Contributor+) Stored Cross-Site Scripting

---

GiveWP <= 2.25.1 – Authenticated (Author+) Stored Cross-Site Scripting

---

GiveWP <= 2.25.1 – Authenticated (Contributor+) Stored Cross-Site Scripting via give_form_grid shortcode

---

W4 Post List <= 2.4.2 – Authenticated (Contributor+) Stored Cross-Site Scripting via ‘w4pl[no_items_text]’

---

GiveWP <= 2.25.1 – Cross-Site Request Forgery to Cross-Site Scripting via render_dropdown

---

Webmention <= 4.0.8 – Reflected Cross-Site Scripting via ‘replytocom’

---

Real Estate 7 Theme <= 3.3.4 – Unauthenticated Arbitrary Email Sending

---

Popup box <= 3.4.4 – Reflected Cross-Site Scripting via ‘ays_pb_tab’ Parameter

---

Paytium: Mollie payment forms & donations <= 4.3.7 – Missing Authorization in ‘pt_cancel_subscription’

---

Paytium: Mollie payment forms & donations <= 4.3.7 – Missing Authorization in ‘update_profile_preference’

---

HT Easy GA4 ( Google Analytics 4 ) <= 1.0.6 – Cross-Site Request Forgery via plugin_activation

---

Updraft Plus <= 1.22.24 – Cross-Site Request Forgery via updraft_ajaxrestore

---

Daily Prayer Time <= 2023.03.08 – Cross-Site Request Forgery

---

Paytium: Mollie payment forms & donations <= 4.3.7 – Missing Authorization in ‘paytium_sw_save_api_keys’

---

GiveWP <= 2.25.1 – Cross-Site Request Forgery via process_bulk_action

---

GiveWP <= 2.25.1 – Authenticated (Contributor+) Arbitrary Content Deletion

---

Mass Delete Unused Tags <= 2.0.0 – Cross-Site Request Forgery via plugin_mass_delete_unused_tags_init

---

Mass Delete Taxonomies <= 3.0.0 – Cross-Site Request Forgery via mp_plugin_mass_delete_tags_init

---

Auto Prune Posts <= 1.8.0 – Cross-Site Request Forgery via admin_menu

---

Drag and Drop Multiple File Upload PRO <= 2.10.9 – Directory Traversal

---

Formidable Forms <= 6.0.1 – IP Spoofing via HTTP header

---

CMP – Coming Soon & Maintenance Plugin by NiteoThemes <= 4.1.6 – Information Exposure

---

RapidLoad Power-Up for Autoptimize <= 1.7.1 – Cross-Site Request Forgery via ‘attach_rule’

---

RapidLoad Power-Up for Autoptimize <= 1.7.1 – Missing Authorization in ‘uucss_update_rule’

---

RapidLoad Power-Up for Autoptimize <= 1.7.1 – Missing Authorization in ‘attach_rule’

---

301 Redirects – Easy Redirect Manager <= 2.72 – Cross-Site Request Forgery via dismiss_notice

---

RapidLoad Power-Up for Autoptimize <= 1.7.1 – Cross-Site Request Forgery via ‘uucss_update_rule’

---

RapidLoad Power-Up for Autoptimize <= 1.7.1 – Missing Authorization in ‘clear_page_cache’

---

Clone <= 2.3.7 – Cross-Site Request Forgery via wp_ajax_tifm_save_decision

---

RapidLoad Power-Up for Autoptimize <= 1.7.1 – Cross-Site Request Forgery via ‘clear_uucss_logs’

---

Popup Maker <= 1.18.0 – Cross-Site Request Forgery via init

---

Affiliate Super Assistent <= 1.5.1 – Cross-Site Request Forgery to Settings Update and Cache Clearing

---

cformsII <= 15.0.4 – Cross-Site Request Forgery leading to Settings Updates

---

Side Menu Lite <= 4.0 – Cross-Site Request Forgery to Item Deletion

---

Clone <= 2.3.7 – Missing Authorization via wp_ajax_tifm_save_decision

---

RapidLoad Power-Up for Autoptimize <= 1.7.1 – Cross-Site Request Forgery via ‘ucss_connect’

---

RapidLoad Power-Up for Autoptimize <= 1.7.1 – Missing Authorization in ‘clear_uucss_logs’

---

External Links <= 2.57 – Cross-Site Request Forgery via action_admin_action_wpel_dismiss_notice

---

Paytium: Mollie payment forms & donations <= 4.3.7 – Missing Authorization in ‘check_for_verified_profiles’

---

RapidLoad Power-Up for Autoptimize <= 1.7.1 – Cross-Site Request Forgery via ‘clear_page_cache’

---

RapidLoad Power-Up for Autoptimize <= 1.7.1 – Missing Authorization in ‘ajax_deactivate’

---

GiveWP <= 2.25.1 – Cross-Site Request Forgery via give_cache_flush

---

GiveWP <= 2.25.1 – Cross-Site Request Forgery via save

---

RapidLoad Power-Up for Autoptimize <= 1.7.1 – Cross-Site Request Forgery via ‘queue_posts’

---

RapidLoad Power-Up for Autoptimize <= 1.7.1 – Cross-Site Request Forgery via ‘ajax_deactivate’

---

Paytium: Mollie payment forms & donations <= 4.3.7 – Missing Authorization in ‘paytium_notice_dismiss’

---

RapidLoad Power-Up for Autoptimize <= 1.7.1 – Missing Authorization in ‘ucss_connect’

---

Paytium: Mollie payment forms & donations <= 4.3.7 – Missing Authorization in ‘check_mollie_account_details’

---

RapidLoad Power-Up for Autoptimize <= 1.7.1 – Missing Authorization in ‘queue_posts’

---

GiveWP <= 2.25.1 – Authenticated (Admin+) Server-Side Request Forgery via give_get_content_by_ajax_handler

---

As a reminder, Wordfence has curated an industry leading vulnerability database with all known WordPress core, theme, and plugin vulnerabilities known as Wordfence Intelligence.

This database is continuously updated, maintained, and populated by Wordfence’s highly credentialed and experienced vulnerability researchers through in-house vulnerability research, vulnerability researchers submitting directly to us using our CVE Request form, and by monitoring varying sources to capture all publicly available WordPress vulnerability information and adding additional context where we can.

Click here to sign-up for our mailing list to receive weekly vulnerability reports like this and important WordPress Security reports in your inbox the moment they are published.

The post Wordfence Intelligence Weekly WordPress Vulnerability Report (Mar 6, 2023 to Mar 12, 2023) appeared first on Wordfence.

Hundreds, if not thousands of WordPress plugins are conceived with the idea of making site building and maintenance easier for site owners. They add features not available in WordPress Core that would otherwise require site owners to write their own code to extend functionality. However, these well-intentioned plugins may sometimes contain seemingly innocuous bugs that can lead to catastrophic consequences.

On Tuesday, February 7th, 2023, prominent WordPress vulnerability researcher István Márton, also known as Lana Codes, reached out to the Wordfence Threat Intelligence team to responsibly disclose an information disclosure vulnerability in Cozmolabs Profile Builder, a WordPress plugin designed to enhance the user profile and registration experience with a reported 60,000+ active installations. If exploited, this vulnerability allows threat actors to gain elevated privileges by taking over arbitrary accounts.

Wordfence researchers quickly assessed the vulnerability and deployed a firewall rule to protect customers from exploitation. Premium, Care, and Response customers received that protection on February 13, 2023 as well as an additional firewall rule for extended protection on February 14, 2023. Sites still running the free version of Wordfence will receive the same protection 30 days later on March 14 and March 15, 2023, respectively.

In coordination with Márton, Cozmolabs quickly released a fix in Profile Builder version 3.9.1 on February 13, 2023, only 6 days after the vulnerability’s discovery.

Vulnerability Summary

Vulnerability Analysis

The vulnerability, assigned CVE-2023-0814, exists due to missing authorization within the wppb_toolbox_usermeta_handler() function. The affected function is defined as a callback function to the ‘user_meta’ shortcode, which is registered via the WordPress add_shortcode() function in usermeta.php.

As with all shortcode callback functions, wppb_toolbox_usermeta_handler() takes an array of attributes. In particular, the ‘user_id’ attribute is used to create a new user object. Then, the ‘key’ attribute is used in a call to ‘$user->get()’. Finally, the function returns the value of the retrieved ‘key’ for the given ‘user_id’. During this process, capability checks are not properly implemented to ensure that the user executing the function is authorized to retrieve the given ‘key’ value.

Prerequisites

Vulnerable instances of Profile Builder need the ‘Enable Usermeta shortcode’ setting enabled within the ‘Shortcodes’ section of the ‘Advanced Settings’ tab of the plugin’s ‘Settings’ page.

Exploitation

Information Disclosure

Any authenticated user, with subscriber-level permissions or greater, can send a specially-crafted HTTP POST request to the ‘wp-admin/admin-ajax.php’ endpoint with the ‘action’ parameter set to ‘parse-media-shortcode’ and the ‘shortcode’ parameter containing the ‘user_meta’ shortcode with the ‘user_id’ and ‘key’ attributes set.

As explained earlier, the value of the ‘key’ attribute is passed to a $user->get() call. Since the get() method of the WP_User class is designed to retrieve user information, any column of the ‘wp_users’ table can be passed via this attribute, including:

• ID
• user_login
• user_pass
• user_nicename
• user_email
• user_url
• user_registered
• user_activation_key
• user_status
• display_name

Password Reset to Privilege Escalation

The Profile Builder plugin provides the shortcode ‘[wppb-recover-password]’ to embed a password recovery form into a page on a WordPress site. The form allows users to submit their username or email address to receive an email with a password reset link containing a user activation key. When generated, this key is stored in the ‘user_activation_key’ column in the ‘wp_users’ table of the WordPress database. Using CVE-2023-0814, this key can be retrieved for any user.

First, the threat actor must generate the user activation key by entering the username or email address of the targeted user in the password recovery form and clicking the ‘Get New Password’ button.

Next, the threat actor will make a similar POST request to our previous user enumeration proof-of-concept, but this time ensuring the ‘user_id’ is set to the user ID of the username or email address entered into the password recovery form and setting the ‘key’ attribute to ‘user_activation_key’.

Once the threat actor has retrieved the user activation key, they can navigate back to the password recovery form page, but this time with the ‘key’ query parameter set to the retrieved user activation key.

At this point, the threat actor simply needs to enter a new password and click the ‘Reset Password’ button. The threat actor will then be able to login using the targeted username and new password.

Timeline

February 7th, 2023 – Lana Codes responsibly discloses the vulnerability to the plugin vendor and our Vulnerability Disclosure program.
February 13th, 2023 – The vendor releases a patch in version 3.9.1 and Wordfence releases a firewall rule to address the vulnerability. Wordfence Premium, Care, and Response users receive this rule.
February 14th, 2023 – Wordfence releases an additional firewall rule to provide extended protection against exploitation. Wordfence Premium, Care, and Response users receive this rule.
March 14th, 2023 – Wordfence free users receive the first firewall rule.
March 15th, 2023 – Wordfence free users receive the second firewall rule.

Conclusion

In today’s post, we covered an Information Disclosure vulnerability that could lead to the takeover of an administrative account in Cozmolabs Profile Builder, a plugin used by over 60,000 WordPress installations. The Wordfence Threat Intelligence team issued a firewall rule providing protection against the vulnerability on February 13th and 14th, 2023. This rule has been protecting our Wordfence Premium, Wordfence Care, and Wordfence Response users since that date, while those still using our free version will receive this rule on March 14 and March 15, 2023.

If you believe your site has been compromised as a result of this vulnerability or any other vulnerability, we offer Incident Response services via Wordfence Care. If you need your site cleaned immediately, Wordfence Response offers the same service with 24/7/365 availability and a 1-hour response time. Both of these products include hands-on support in case you need further assistance. If you have any friends or colleagues who are using this plugin, please share this announcement with them and encourage them to update to the latest patched version of Profile Builder as soon as possible.

If you are a security researcher, you can responsibly disclose your finds to us and obtain a CVE ID and get your name on the Wordfence Intelligence leaderboard.

The post Vulnerability Patched in Cozmolabs Profile Builder Plugin – Information Disclosure Leads to Account Takeover appeared first on Wordfence.

Wordfence has curated an industry leading vulnerability database with all known WordPress core, theme, and plugin vulnerabilities known as Wordfence Intelligence.

This database is continuously updated, maintained, and populated by Wordfence’s highly credentialed and experienced vulnerability researchers through in-house vulnerability research, vulnerability researchers submitting directly to us using our CVE Request form, and by monitoring varying sources to capture all publicly available WordPress vulnerability information and adding additional context where we can.

Our mission with Wordfence Intelligence is to make valuable vulnerability information easily accessible to everyone, like the WordPress community, so individuals and organizations alike can utilize that data to make the internet more secure. That is why the Wordfence Intelligence user interface and vulnerability API are completely free to access and utilize both personally and commercially.

Last week, there were 117 vulnerabilities disclosed in WordPress based software that have been added to the Wordfence Intelligence Vulnerability Database, and there were 30 Vulnerability Researchers that contributed to WordPress Security last week. You can find those vulnerabilities below along with some data about the vulnerabilities that were added.

Click here to sign-up for our mailing list to receive weekly vulnerability reports like this and important WordPress Security reports in your inbox the moment they are published.

---

Total Unpatched & Patched Vulnerabilities Last Week

Patch Status	Number of Vulnerabilities
Unpatched	44
Patched	73

---

Total Vulnerabilities by CVSS Severity Last Week

Severity Rating	Number of Vulnerabilities
Low Severity	1
Medium Severity	104
High Severity	10
Critical Severity	2

---

Total Vulnerabilities by CWE Type Last Week

Vulnerability Type by CWE	Number of Vulnerabilities
Cross-Site Request Forgery (CSRF)	53
Improper Neutralization of Input During Web Page Generation (‘Cross-site Scripting’)	34
Missing Authorization	16
Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’)	2
Information Exposure	2
Authorization Bypass Through User-Controlled Key	2
Server-Side Request Forgery (SSRF)	2
Incorrect Privilege Assignment	1
Unrestricted Upload of File with Dangerous Type	1
Improper Neutralization of Special Elements in Output Used by a Downstream Component (‘Injection’)	1
Protection Mechanism Failure	1
Improper Control of Filename for Include/Require Statement in PHP Program (‘PHP Remote File Inclusion’)	1
Improper Validation of Integrity Check Value	1

---

Researchers That Contributed to WordPress Security Last Week

Researcher Name	Number of Vulnerabilities
Lana Codes	27
Rio Darmawan	20
Mika	13
Dave Jong	6
FearZzZz	4
Erwan LR	4
yuyudhn	4
WPScanTeam	3
Prasanna V Balaji	3
Marco Wotschka	3
Rafie Muhammad	3
TEAM WEBoB of BoB 11th	2
Abdi Pranata	2
Muhammad Daffa	2
Nguyen Xuan Chien	2
Marc-Alexandre Montpas	1
TaeEun Lee	1
Pounraj Chinnasamy	1
Jarko Piironen	1
dc11	1
rezaduty	1
Mohammed El Amin, Chemouri	1
Universe	1
Alex Sanford	1
Vaibhav Rajput	1
MyungJu Kim	1
Mahesh Nagabhairava	1
Leonidas Milosis	1
Shreya Pohekar	1
Nguyen Thuc Tuyen	1

 

Are you a security researcher who would like to be featured in our weekly vulnerability report? You can responsibly disclose your WordPress vulnerability discoveries to us and obtain a CVE ID through this form. Responsibly disclosing your vulnerability discoveries to us will also get your name added on the Wordfence Intelligence leaderboard along with being mentioned in our weekly vulnerability report.

---

Vulnerability Details

Houzez <= 2.7.1 – Privilege Escalation

---

Debug Assistant <= 1.4 – Cross-Site Request Forgery via imlt_create_admin

---

OceanWP <= 3.4.1 – Authenticated (Subscriber+) Local File Inclusion

---

ProfileGrid <= 5.3.0 – Missing Authorization to Arbitrary Password Reset

---

CSSTidy – Server-Side Request Forgery

---

Gallery Blocks with Lightbox <= 3.0.7 – Missing Authorization in pgc_sgb_add_dashboard_widget

---

Paid Memberships Pro <= 2.9.11 – Authenticated (Subscriber+) SQL Injection via Shortcodes

---

Types <= 3.4.17 – Unauthenticated (Administrator+) Arbitrary File Upload

---

Leyka <= 3.29.2 – Unauthenticated Stored Cross-Site Scripting

---

Dokan <= 3.7.12 – Authenticated (Vendor+) SQL Injection

---

LWS Tools <= 2.3.1 – Cross-Site Request Forgery

---

Manage Upload Limit <= 1.0.4 – Reflected Cross-Site Scripting via upload_limit

---

Woodmart <= 7.1.1 – Cross-Site Request Forgery to License Update

---

Shortcodes Ultimate <= 5.12.7 – Authenticated (Subscriber+) Information Exposure

---

WoodMart <= 7.1.1 – Missing Authorization to Shortcode Injection

---

Sales Report Email for WooCommerce <= 2.8 – Missing Authorization for Email Functionality

---

Smart Slider 3 <= 3.5.1.13 – Authenticated (Contributor+) Stored Cross-Site Scripting

---

Simple Vimeo Shortcode <= 2.9.1 – Authenticated (Contributor+) Stored Cross-Site Scripting via shortcode

---

Cost Calculator <= 1.8 – Authenticated (Contributor+) Stored Cross-Site Scripting

---

menu shortcode <= 1.0 – Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode

---

WordPress Infinite Scroll – Ajax Load More <= 5.6.0.2 – Authenticated (Contributor+) Stored Cross Site Scripting via Shortcode

---

Cookie Notice & Compliance for GDPR / CCPA <= 2.4.6 – Authenticated (Contributor+) Stored Cross-Site Scripting via shortcodes

---

Yoast SEO <= 20.2 – Authenticated (Contributor+) Cross-Site Scripting

---

NEX-Forms – Ultimate Form Builder <= 8.3 – Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode

---

Real Estate 7 <= 3.3.4 – Reflected Cross-Site Scripting via ct_additional_features

---

Watu Quiz <= 3.3.9 – Reflected Cross-Site Scripting

---

Darcie <= 1.1.5 – Reflected Cross-Site Scripting via JS split

---

GN Publisher <= 1.5.5 – Reflected Cross-Site Scripting

---

Easy Testimonial Slider and Form <= 1.0.15 – Unauthenticated Reflected Cross-Site Scripting via search_term

---

GTmetrix for WordPress <= 0.4.5 – Reflected Cross-Site Scripting via ‘url’

---

Cart Lift – Abandoned Cart Recovery for WooCommerce and EDD <= 3.1.5 – Reflected Cross-Site Scripting via cart_search

---

Real Estate 7 <= 3.3.4 – Cross-Site Request Forgery

---

Instant Images <= 5.1.0.1 – Authenticated (Author+) Server-Side Request Forgery via instant_images_download

---

Leyka <= 3.29.2 – Cross-Site Request Forgery

---

Rife Elementor Extensions & Templates <= 1.1.10 – Missing Authorization via import_templates

---

Sheets To WP Table Live Sync <= 2.12.15 – Cross-Site Request Forgery

---

Advanced Text Widget <= 2.1.2 – Missing Authorization via atw_dismiss_admin_notice

---

WP SMS <= 6.0.4 – Information Disclosure via REST API

---

Metform Elementor Contact Form Builder <= 3.2.1 – reCaptcha Protection Bypass

---

Event Espresso 4 Decaf <= 4.10.44.decaf – Feature Bypass

---

WP Repost <= 0.1 – Missing Authorization

---

Simple CSV/XLS Exporter <= 1.5.8 – CSV Injection

---

Advanced Text Widget <= 2.1.2 – Authenticated (Administrator+) Stored Cross-Site Scripting

---

Jetpack CRM <= 5.4.4 – Authenticated (Administrator+) Stored Cross-Site Scripting

---

We’re Open! <= 1.46 – Authenticated (Administrator+) Stored Cross-Site Scripting

---

WP Repost <= 0.1 – Authenticated (Administrator+) Stored Cross-Site Scritping

---

Button Generator – easily Button Builder <= 2.3.3 – Authenticated (Administrator+) Stored Cross-Site Scripting

---

Dashboard Widgets Suite <= 3.2.1 – Authenticated (Administrator+) Stored Cross-Site Scripting

---

Publish to Schedule <= 4.5.4 – Authenticated (Administrator+) Stored Cross-Site Scripting

---

Namaste! LMS <= 2.5.9.9 – Authenticated (Administrator+) Stored Cross-Site Scripting via ‘accept_other_payment_methods’, ‘other_payment_methods’ Parameters

---

FareHarbor for WordPress <= 3.6.6 – Authenticated (Administrator+) Stored Cross-Site Scripting

---

CPO Content Types <= 1.1.0 – Authenticated (Administrator+) Stored Cross-Site Scripting

---

WP No External Links <= 1.0.2 – Authenticated (Administrator+) Stored Cross-Site Scritping

---

Simple File List <= 6.0.9 – Authenticated (Administrator+) Stored Cross-Site Scripting

---

New Adman <= 1.6.8 – Authenticated (Administrator+) Stored Cross-Site Scripting

---

Simple Slug Translate <= 2.7.2 – Authenticated (Administrator+) Stored Cross-Site Scritping

---

JCH Optimize <= 3.2.2 – Authenticated (Administrator+) Stored Cross-Site Scripting via admin settings

---

Debug Assistant <= 1.4 – Authenticated (Administrator+) Stored Cross-Site Scripting

---

Maspik – Spam blacklist <= 0.7.8 – Cross-Site Request Forgery

---

WpStream – Live Streaming, Video on Demand, Pay Per View <= 4.4.10 – Cross-Site Request Forgery via wpstream_settings

---

WP Time Slots Booking Form <= 1.1.76 – Cross-Site Request Forgery to Feedback Submission

---

Download Read More Excerpt Link <= 1.6.0 – Cross-Site Request Forgery to Settings Update

---

CP Contact Form with Paypal <= 1.3.34 – Authenticated Feedback Submission

---

WP Google Tag Manager <= 1.1 – Cross-Site Request Forgery

---

DeepL Pro API translation <= 2.1.4 – Cross-Site Request Forgery via saveSettings

---

Search in Place <= 1.0.104 – Missing Authorization to Feedback Submission

---

WP Meteor Page Speed Optimization Topping <= 3.1.4 -Missing Authorization to Notice Dismissal

---

Preview Link Generator <= 1.0.3 – Cross-Site Request Forgery to Arbitrary Plugin Activation

---

Blog Floating Button <= 1.4.12 – Cross-Site Request Forgery

---

Free WooCommerce Theme 99fy Extension <= 1.2.7 – Cross-Site Request Forgery leading to Arbitrary Plugin Activation

---

Shortcodes Ultimate <= 5.12.7 – Authenticated (Subscriber+) Arbitrary Post Access via Shortcode

---

WP Insurance – WordPress Insurance Service Plugin <= 2.1.3 – Cross-Site Request Forgery leading to Arbitrary Plugin Activation

---

WC Sales Notification <= 1.2.2 – Cross-Site Request Forgery to Arbitrary Plugin Activation

---

WP Meteor Page Speed Optimization Topping <= 3.1.4 – Cross-Site Request Forgery via processAjaxNoticeDismiss

---

HT Portfolio <= 1.1.4 – Cross-Site Request Forgery to Arbitrary Plugin Activation

---

Add Expires Headers & Optimized Minify <= 2.7 – Cross-Site Request Forgery via [placeholder]

---

HT Politic <= 2.3.7 – Cross-Site Request Forgery leading to Arbitrary Plugin Activation

---

DecaLog <= 3.7.0 – Cross-Site Request Forgery via get_settings_page

---

WP Plugin Manager <= 1.1.7 – Cross-Site Request Forgery to Arbitrary Plugin Activation

---

About Me 3000 widget <= 2.2.6 – Cross-Site Request Forgery to Plugin Settings Update

---

ClickFunnels <= 3.1.1 – Cross-Site Request Forgery to Settings Update

---

Fontiran <= 2.1 – Cross-Site Request Forgery

---

Ever Compare <= 1.2.3 – Cross-Site Request Forgery to Arbitrary Plugin Activation

---

WP TFeed <= 1.6.9 – Cross-Site Request Forgery via aptf_delete_cache

---

Resize at Upload Plus <= 1.3 – Cross-Site Request Forgery

---

WP Social Bookmarking Light <= 2.0.7 – Cross-Site Request Forgery

---

Total Poll Lite <= 4.8.6 – Cross-Site Request Forgery

---

HT Slider For Elementor <= 1.3.9 – Cross-Site Request Forgery to Arbitrary Plugin Activation

---

When Last Login <= 1.2.1 – Cross-Site Request Forgery via wll_hide_subscription_notice

---

HT Event <= 1.4.5 – Cross-Site Request Forgery leading to Arbitrary Plugin Activation

---

WP Time Slots Booking Form <= 1.1.76 – Missing Authorization to Feedback Submission

---

WP Clean Up <= 1.2.3 – Cross-Site Request Forgery via wp_clean_up_optimize

---

WP Shamsi <= 4.3.3 – Missing Authorization leading to Authenticated (Subscriber+) Attachment Deletion

---

WP Education <= 1.2.6 – Cross-Site Request Forgery to Arbitrary Plugin Activation

---

Calculated Fields Form <= 1.1.120 – Missing Authorization to Feedback Submission

---

Quiz And Survey Master <= 8.0.10 – Cross-Site Request Forgery to Quiz Restoration

---

Smart YouTube PRO <= 4.3 – Cross-Site Request Forgery via handle_colorbox_options

---

Big Store <= 1.9.3 – Cross-Site Request Forgery to Arbitrary Plugin Activation

---

WP Translitera <= p1.2.5 – Cross-Site Request Forgery

---

WP Film Studio <= 1.3.4 – Cross-Site Request Forgery to Arbitrary Plugin Activation

---

XML Sitemap Generator for Google <= 1.2.8 – Cross-Site Request Forgery to Plugin Settings Changes

---

New Adman <= 1.6.8 – Cross-Site Request Forgery via plugin_menu

---

QuickSwish <= 1.0.9 – Cross-Site Request Forgery to Arbitrary Plugin Activation

---

OoohBoi Steroids for Elementor <= 2.1.3 – Missing Authorization leading to Authenticated (Subscriber+) Attachment Deletion

---

Fontiran <= 2.1 – Cross-Site Request Forgery

---

Total Theme <= 2.1.19 – Authenticated(Subscriber+) Plugin Activation

---

Classic Editor and Classic Widgets <= 1.2.4 – Cross-Site Request Forgery via render_settings_page

---

Rus-To-Lat <= 0.3 – Cross-Site Request Forgery to Plugins Options Changes

---

Elegant Custom Fonts <= 1.0 – Cross-Site Request Forgery

---

OptinMonster <= 2.12.1 – Authenticated (Subscriber+) Sensitive Information Disclosure via Shortcode

---

Contact Form 7 Widget For Elementor Page Builder & Gutenberg Blocks <= 1.1.5 – Cross-Site Request Forgery to Arbitrary Plugin Activation

---

Calculated Fields Form <= 1.1.120 – Cross-Site Request Forgery

---

Search in Place <= 1.0.104 – Cross-Site Request Forgery to Feedback Submission

---

WP News <= 1.1.9 – Cross-Site Request Forgery to Arbitrary Plugin Activation

---

OAuth Single Sign On – SSO (OAuth Client) <= 6.24.1 – Cross-Site Request Forgery via ‘delete’ in mooauth_client_applist_page

---

Wholesale Suite <= 2.1.5 – Missing Authorization to Plugin Settings Change

---

FluentSMTP <= 2.2.2 – Authenticated (Author+) Stored Cross-Site Scripting via Email Logs

---

Click here to sign-up for our mailing list to receive weekly vulnerability reports like this and important WordPress Security reports in your inbox the moment they are published.

The post Wordfence Intelligence Weekly WordPress Vulnerability Report (Feb 27, 2023 to Mar 5, 2023) appeared first on Wordfence.

In the cybersecurity field, we talk a lot about threat actors and vulnerable code, but what doesn’t get discussed enough is intentional vulnerabilities and becoming your own threat actor. Even when making decisions with the best of intentions, it is possible to work against your own best interests. One area we see this in comes from website developers trying to safeguard their work. It can be tempting to incorporate code that gives the developer access to the site files, also known as a backdoor, in the event that the client chooses not to pay, so that the developer can remove their code or otherwise damage the site.

While implementing a backdoor may seem like a viable solution to protect your resource investment, it comes with potential ethical and legal problems, in addition to the added security risks of a backdoor hardcoded into the website. There are always better options available, even if they are less convenient for the client and developer. When developing a website, the developer should keep in mind that their needs are just as important as the client’s. Keeping this in mind will help to prevent the situations that may lead to the implementation of a backdoor on the website.

One of the biggest reasons a web developer may be tempted to include a hardcoded backdoor is to ensure their work is not used without payment. A common practice among website developers is to require 50% of the development fee up front, with the remaining sum paid upon delivery of the completed project. Especially among freelance developers, it is not uncommon to begin development even before the initial fees are paid, and even provide the final code before the final payment is received. The fear of a client not making a payment may cause a developer to believe that it is a good idea to hard code a backdoor into the project, so that the developer can remove their code or take down the site entirely as a form of retaliation.

What should be obvious is that intentionally damaging a website is a violation of laws in many countries, and could lead to fines or even jail time. In the United States, the Computer Fraud and Abuse Act of 1986 (CFAA) clearly defines illegal use of computer systems. According to 18 U.S.C. § 1030 (e)(8), simply accessing computer systems in a way that uses higher privileges or access levels than permitted is a violation of the law. Further, intentionally damaging the system or data is also a crime. The penalty for violating the CFAA can include sentences 10 years or more in prison, in addition to large financial penalties.

Let’s say a developer uses a backdoor on a website they worked on simply to access the files in an unapproved manner. Even if they do not cause any damage to the system or files, the developer could face fines of $5,000 and up to five years in prison. Use of the backdoor to take the site down or otherwise damage the files or system, might lead to even more jail time and even larger fines. It could be argued that these penalties are excessive, but it’s also important to remember that they are intended as deterrents since most threat actors are never caught.

As it stands, however, freelance developers trying to protect their work are much more likely to be caught and prosecuted than scammers in countries without an extradition arrangement. An unscrupulous client who is familiar with the law could also use the threat of prosecution to extort further unpaid labor from a freelance developer who backdoored their site.

Even beyond potential legal ramifications, these practices can lead to negative word-of-mouth, which can damage the reputation of the developer. Even if the developer is able to avoid legal issues from these actions, being perceived as unethical can negatively impact future profits, and even cause a business to fail.

Another consideration is the fact that a backdoor adds a potential vulnerability to the client’s website. If the developer is able to access the site through illegitimate means, then a potential attacker may be able to use the same method to access the site’s files. Security should always be a consideration when developing a website or one of its features. Implementing insecure code can lead to similar consequences as intentionally damaging a website.

Rather than adding a backdoor into a client’s website, it is better to set clear expectations with a client regarding deliverables, and how they will be impacted by late or missing payments. It is crucial to use written contracts to specify these expectations. If possible, start with a standard written contract that all clients are required to sign and have an attorney review it for potential issues.

If there is an agreement in place that outlines the fact that no code will be provided without full payment, then the developer is under no obligation to implement the code on the production server until they have been fully paid. A development server under the developer’s control should always be used, and once agreements have been met, the code can be moved from the development server to the client’s production server.

Note: This is not intended as legal advice and we recommend familiarizing yourself with all applicable laws and consulting with a licensed legal professional in your area.

The post PSA: Intentionally Leaving Backdoors in Your Code Can Lead to Fines and Jail Time appeared first on Wordfence.

Last August, at Black Hat 2022 in Las Vegas, we launched Wordfence Intelligence, a product designed to provide large enterprise customers with rich IP threat data, malware signatures, malware hashes, and vulnerability data to help keep enterprise customers and networks secure.

Our mission at Wordfence is to secure the WordPress community, and to that end we launched a product called “Wordfence Intelligence Community Edition” shortly after the Black Hat launch, in December of last year. This launch expressed a point of view: We believe that vulnerability data is community property because it is created by the security community. While our researchers contribute a significant amount of research, we didn’t feel right about claiming vulnerability data as our own intellectual property and selling it. That is why we included the entire enterprise vulnerability database in this free product, and made API access to the data completely free.

Our goal going forward is to invest in the Wordfence Intelligence WordPress vulnerability database and the distribution of vulnerabilities to the community, and we think that the phrase “community edition” makes the product sound like a lesser version of what might be available to paying customers. That is entirely inaccurate. There is no “paid version” of our vulnerability database – the free edition is the best available and our goal is to make the Wordfence Intelligence WordPress vulnerability database the best and most current source for WordPress vulnerability data in the world.

That is why we have decided to rebrand “Wordfence Intelligence Community Edition” simply to “Wordfence Intelligence”.

---

---

From now on, we will use the phrase “Wordfence Intelligence Enterprise” to describe paid-only products designed for use by large organizations defending networks and large customer bases, and “Wordfence Intelligence” will be the suite of products available at no cost to defenders and to the research community.

During 2023 you will see several exciting new features added to Wordfence Intelligence designed to secure the WordPress community, to make data freely available to threat researchers, and to incentivize the research community to help secure WordPress. As a team we are incredibly excited about the free resources that Wordfence Intelligence makes available to the global security community and how that will improve WordPress security as a whole. You can find Wordfence Intelligence (and its free community resources) on this page.

In addition, you can learn how to access the Wordfence Intelligence vulnerability data via an API on this page – the data is available to download in its entirety, at no cost, as often as you’d like!

If you are an enterprise customer, you can learn more about our enterprise products on the product page for Wordfence Intelligence Enterprise.

Thanks for choosing Wordfence, and we look forward to keeping your WordPress sites secure and to securing the global WordPress community.

– Mark Maunder – Wordfence Founder & CEO and Chloe Chamberland, Head of Product for Wordfence Intelligence

The post Wordfence Intelligence: Because Community Created Vulnerabilities Are Community Property appeared first on Wordfence.