WOLF โ€“ WordPress Posts Bulk Editor and Manager Professional <= 1.0.8.1 - Cross-Site Request Forgery

5.4
Cross-Site Request Forgery (CSRF)
CVE CVE-2024-0790
CVSS 5.4 (Medium)
Publicly Published January 30, 2024
Last Updated February 5, 2024
Researcher Francesco Carlucci

Description

The WOLF โ€“ WordPress Posts Bulk Editor and Manager Professional plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.8.1. This is due to missing or incorrect nonce validation on the wpbe_create_new_term, wpbe_update_tax_term, and wpbe_delete_tax_term functions. This makes it possible for unauthenticated attackers to create, modify and delete taxonomy terms via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. Furthermore, the functions wpbe_save_options, wpbe_bulk_delete_posts_count, wpbe_bulk_delete_posts, and wpbe_save_meta are vulnerable to Cross-Site Request Forgery allowing for plugin options update, post count deletion, post deletion and modification of post metadata via forged request.

References

Share

Vulnerability Details for WOLF โ€“ WordPress Posts Bulk Editor and Manager Professional

Software Type Plugin
Software Slug bulk-editor (view on wordpress.org)
Patched? Yes
Remediation Update to version 1.0.8.2, or a newer patched version
Affected Version
  • <= 1.0.8.1
Patched Version
  • 1.0.8.2

Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!

Learn more

Want to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.

Get Wordfence

The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.

Documentation