A privilege management vulnerability exists in the UpdraftPlus: WP Backup & Migration Plugin for WordPress before versions 2.26.16.26 and 1.26.16. This flaw allows users with the Subscriber role to inject SQL code into backup data, which is then executed when an administrator restores the backup. This can lead to privilege escalation, such as granting the attacker administrator rights.
A deserialization vulnerability (CWE-502) exists in the UpdraftPlus: WP Backup & Migration Plugin for WordPress versions before 2.26.16.26 and 1.26.16. This flaw allows users with Subscriber-level roles to plant serialized data that becomes a PHP Object Injection when an administrator performs a backup and restore operation. No known gadget chains currently exist, limiting the demonstrated impact to instantiation of attacker-chosen classes in their own requests. Exploitation requires precise alignment of the planted data with the backup restore process.
A privilege escalation vulnerability exists in the UpdraftPlus: WP Backup & Migration Plugin for WordPress versions before 2.26.16.26 and 1.26.16. It arises from improper handling of comment-like content within long SQL statements during database backup restoration. This flaw allows users with Subscriber roles who have crafted malicious content in their profiles to execute SQL commands when an administrator restores a backup, escalating their privileges to administrator.
Mapster WP Maps — Mapbox, MapLibre & Google Maps for WordPress plugin versions before 2.0.7 contain an authorization bypass vulnerability. Authenticated users with Contributor-level access can overwrite titles, content, and metadata of any post, page, or media attachment regardless of ownership due to missing authorization checks when saving edits via the bundled photo-gallery library.
GiveWP WordPress plugin versions before 4.19.2.1 contain a vulnerability that allows authenticated users who own a donor record to access sensitive donor information via a REST API endpoint. This includes email addresses, phone numbers, names, postal addresses, and company details of all donors.
The Video Conferencing with Zoom WordPress plugin before version 4.7.0 allows unauthenticated users to access details of Zoom meeting recordings if they know the meeting ID. This occurs because the plugin does not verify whether the recordings were published on the site before retrieving them via the connected Zoom account. Exposed information includes the meeting topic, share link, passcode (when returned by Zoom), and direct play and download links.
The Video Conferencing with Zoom WordPress plugin versions prior to 4.7.0 have a vulnerability where unauthorized users can access meeting join links without proper authorization checks. This includes meetings that are restricted to logged-in users, password-protected, or unpublished. The vulnerability allows exposure of passcode-embedded join links to unauthenticated users.
The Video Conferencing with Zoom WordPress plugin versions from 4.6.8 up to but not including 4.7.0 contains an improper authentication vulnerability. It does not verify that a requester is authorized to join a meeting before issuing a Zoom Meeting SDK signature, allowing unauthenticated users to obtain valid signed join credentials for arbitrary meetings. This issue is fixed in version 4.7.0.
A vulnerability in the GiveWP WordPress plugin before version 4.19.2.1 allows unauthenticated users to access the names of donors who chose to give anonymously via a public REST API endpoint.
UpdraftPlus: WP Backup & Migration Plugin versions before 1.26.10 and 2.26.10.26 contain an improper privilege management vulnerability. A Subscriber-level user can exploit a second-order SQL injection in the database restore process to escalate privileges to administrator. This issue is due to an incomplete fix of a previous vulnerability (CVE-2026-108761), where only one execution path was secured, leaving another exploitable.
The Restrictions for BuddyPress WordPress plugin up to version 1.5.4 contains a critical remote code execution vulnerability. This flaw arises from unsafe use of eval() on attacker-controlled input embedded in a double-quoted PHP string, allowing unauthenticated attackers to execute arbitrary code via a crafted GET request. The vulnerability is exploitable without authentication or special plugin configuration if BuddyPress and Paid Memberships Pro are active alongside this plugin.
The Salon Booking System plugin for WordPress up to version 10.31.16 contains an authorization bypass vulnerability. Authenticated users with subscriber-level access or higher can overwrite arbitrary user meta fields, including those of administrator accounts, and create bookings attributed to any user. This occurs because the plugin does not properly verify user authorization, and the default configuration disables reCAPTCHA, allowing the booking endpoint's permission check to succeed for any authenticated user.
The Coupon Creator WordPress plugin up to version 3.6.5 contains a stored cross-site scripting (XSS) vulnerability via the 'post_title' parameter. This flaw allows authenticated users with author-level or higher privileges to inject malicious scripts that execute when other users view the affected pages. Exploitation requires the 'Disable Print View' option to be enabled by an administrator, which is not the default setting.
The Coupon Creator plugin for WordPress up to version 3.6.5 contains a stored cross-site scripting (XSS) vulnerability via the 'metavalue' parameter when used with the 'metakeyinput=cctor_expiration' parameter. Authenticated users with contributor-level access or higher can inject arbitrary scripts that execute when a user views the affected page. This occurs due to insufficient input sanitization and output escaping, combined with WordPress core behavior that allows raw HTML storage for unregistered meta keys.
The Booking Calendar WordPress plugin up to version 12.0 is vulnerable to stored Cross-Site Scripting (XSS) via its 'booking' shortcode. Authenticated users with contributor-level access or higher can inject malicious scripts that execute when other users view the affected pages. This vulnerability arises from insufficient input sanitization and output escaping of user-supplied attributes.
The Fastcache plugin by Host.it for WordPress has a reflected cross-site scripting (XSS) vulnerability in the 's' parameter affecting all versions up to and including 1.7.14. This vulnerability arises from insufficient input sanitization and output escaping when both the Light Images feature and the DOMDocument entity-decode branch are enabled, which is the default configuration. An unauthenticated attacker could exploit this by tricking a user into clicking a crafted link, causing arbitrary scripts to execute in the user's browser.
A flaw was found in Quay. Insufficient validation of repository notification webhook URLs allows an authenticated administrator to trigger Server-Side Request Forgery (SSRF). By specifying an internal URL or a redirect to an internal destination, an attacker can force the Quay worker to issue unauthorized HTTP requests to internal network locations and cloud metadata services.
The rtMedia plugin for WordPress, BuddyPress, and bbPress contains a stored DOM-based cross-site scripting (XSS) vulnerability in the 'media_title' parameter affecting all versions up to 4.7.18. Authenticated users with subscriber-level access or higher can inject malicious scripts that execute when other users load the affected pages via the Backbone.js-rendered "Load More" pagination. The server-side PHP rendering is not vulnerable due to proper escaping.
The WP Import Export Lite WordPress plugin up to version 3.9.32 contains a vulnerability that allows unauthenticated attackers to inject arbitrary PHP callables via a specially crafted comment containing a malicious shortcode. Exploitation requires an administrator to perform a routine export-import workflow, but the attacker only needs the ability to submit a pending comment on a comments-open post.
The npm package @pkgship/frps-windows-amd64 version 0.71.1 contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected computer should be rotated immediately from a different, secure machine. Removal of the package alone does not guarantee eradication of the malicious software, as full control may have been given to an external attacker.