Latest

Most recently published vulnerabilities

Back to overview
RoutineCVE-2026-131730publishpress · publishpress revisionsWordPress PublishPress Revisions plugin <= 4.3.3 - Broken Access Control vulnerabilityMissing Authorization vulnerability in PublishPress PublishPress Revisions revisionary allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects PublishPress Revisions: from n/a through 4.3.3.CVSS4.3MediumRoutineCVE-2026-131728nickboss · wordpress file uploadWordPress WordPress File Upload plugin <= 5.2.4 - Sensitive Data Exposure vulnerabilityInsertion of Sensitive Information Into Sent Data vulnerability in Nickboss WordPress File Upload wp-file-upload allows Retrieve Embedded Sensitive Data.This issue affects WordPress File Upload: from n/a through 5.2.4.CVSS5.3MediumRoutineCVE-2026-130624wpkoi wordpress themes · wpkoi templates for elementorWordPress WPKoi Templates for Elementor plugin <= 3.7.5 - Cross Site Scripting (XSS) vulnerabilityImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WPKoi WordPress Themes WPKoi Templates for Elementor wpkoi-templates-for-elementor allows Stored XSS.This issue affects WPKoi Templates for Elementor: from n/a through 3.7.5.CVSS6.5MediumRoutineCVE-2026-129086wedevs · happy addons for elementorWordPress Happy Addons for Elementor plugin <= 3.51.3 - Cross Site Scripting (XSS) vulnerabilityImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in weDevs Happy Addons for Elementor happy-elementor-addons allows Stored XSS.This issue affects Happy Addons for Elementor: from n/a through 3.51.3.CVSS6.5MediumRoutineCVE-2026-131789mycredWordPress myCred plugin <= 4.0.3 - Broken Access Control vulnerabilityMissing Authorization vulnerability in myCred myCred mycred allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects myCred: from n/a through 4.0.3.CVSS5.3MediumRoutineCVE-2026-131787liquid web / stellarwp · gutenberg blocks by kadence blocksWordPress Gutenberg Blocks by Kadence Blocks plugin <= 3.9.1.1 - Cross Site Scripting (XSS) vulnerabilityImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Liquid Web / StellarWP Gutenberg Blocks by Kadence Blocks kadence-blocks allows Stored XSS.This issue affects Gutenberg Blocks by Kadence Blocks: from n/a through 3.9.1.1.CVSS6.5MediumRoutineCVE-2026-131781brainstorm force · spectraWordPress Spectra plugin <= 2.20.6 - Cross Site Scripting (XSS) vulnerabilityImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Brainstorm Force Spectra ultimate-addons-for-gutenberg allows Stored XSS.This issue affects Spectra: from n/a through 2.20.6.CVSS6.5MediumRoutineCVE-2026-131732magepeople inc. · taxi booking manager for woocommerceWordPress Taxi Booking Manager for WooCommerce plugin <= 2.2.10 - Broken Access Control vulnerabilityMissing Authorization vulnerability in Magepeople inc. Taxi Booking Manager for WooCommerce ecab-taxi-booking-manager allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Taxi Booking Manager for WooCommerce: from n/a through 2.2.10.CVSS4.3MediumRoutineCVE-2026-131785publishpress · publishpress permissionsWordPress PublishPress Permissions plugin <= 5.0.1 - Broken Access Control vulnerabilityMissing Authorization vulnerability in PublishPress PublishPress Permissions press-permit-core allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects PublishPress Permissions: from n/a through 5.0.1.CVSS5.3MediumRoutineCVE-2026-131170pretixInsufficient validation of payment status for StripeOur payment integration with Stripe did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment. However, the attack requires knowledge of a valid charge ID from the same event which we believe is usually not exposed to users. To simplify attack surface, the fix removes support for incoming webhooks regarding payments created through Stripe's old "source" API. pretix stopped creating payments using this API in 2024.1 for most payment methods and in 2024.9 for all payment methods.CVSS6.3MediumRoutineCVE-2026-131169pretixPermissions are copied when copying scheduled exportsWhen a scheduled export is copied, the permissions of the original export's owner are used when running the export. This allows users to create exports with data they usually shouldn't be able to see, but only within events they already have permissions to.CVSS2.1LowRoutineCVE-2026-131168pretixValidation bypass allows buying sold-out productsA legacy code path allowed users to craft requests to a ticket shop that bypass some validation steps for the selected products. In consequence, this could lead to an attacker purchasing products that are in fact sold out.CVSS6.6MediumPrioritiseCVE-2026-131167pretixUnsafe usage of return valuespretix offloads certain processes to background tasks that are run by a different server to avoid HTTP workers being clogged with processes that take longer than a usual web request. The browser periodically polls the server to see if the task is already finished using a UUID-shaped task ID. Once the task is completed, pretix resumes to the next step of the operation based on the result of the task. The system does however not check if the result stems from the correct type of task. Therefore, an attacker can supply the UUID of a task of a different type and pretix will continue with the result from the wrong task. In most cases, this will just result in an error because the return types do not match up, but in some cases this can be abused to extract objects the attacker usually should not see. Specifically, a vector was discovered that allowed to abuse this for unauthorized access to other people's ticket purchases. The attacker can, however, not control which purchases they get access to.CVSS8.9HighRoutineCVE-2026-131166pretixIncorrect device security profileWhen configuring a device to use the security profile "pretixSCAN (kiosk mode, no order sync, no search)", the API search endpoint introduced in pretix 4.12 was not blocked correctly. This theoretically allows these devices to perform searches for orders even if that was not intended. If the device is in kiosk mode, the search button will still be hidden from users.CVSS6.0MediumRoutineCVE-2026-131165pretixIncorrect check of permissions in scheduled exportsThe fix for CVE-2026-127174 published in 2026.9.2 is incomplete: When expanding an export from "some events" to "all events", it is checked that the acting user is part of a team with permission to all events, but this check is not correctly bound to the organizer and could also be passed through permissions on a different organizer.CVSS2.1LowRoutineCVE-2026-131164pretixLink to parent order or ticket exposed in certain conditionsWhen a ticket holder opens the ticket page of a ticket that is an add-on (possible since 2026.9) the HTML content of the page contains the secret link to the parent product, creating a potential data leak. Under different specific conditions, when a ticket contains user-uploaded files in response to a question, the page can even contain the secret link to the entire order.CVSS2.3LowRoutineCVE-2026-131163pretix · pretix-adyenStored XSS in pretix-adyenA stored XSS in pretix-adyen has been discovered where an attacker could configure his own ticket shop in a way that API calls are not made to Adyen, but an attacker-controlled server. Results of these API calls would then be embedded in a part of the shop without proper escaping, leading to full XSS including potential session takeover.CVSS8.6HighPrioritiseCVE-2026-131804seraphinitesoft · seraphinite acceleratorSeraphinite Accelerator <= 2.31 - Unauthenticated Stored Cross-Site Scripting via 'User-Agent' HTTP HeaderThe Seraphinite Accelerator plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'HTTP_USER_AGENT' parameter in all versions up to, and including, 2.31 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires that an administrator has previously enabled the 'Enable logging' and 'HTTP trace' diagnostic options in the plugin's Advanced → Debug settings, both of which are disabled by default.CVSS7.2HighRoutineCVE-2026-131783mycredWordPress myCred plugin <= 4.0.3 - Broken Access Control vulnerabilityMissing Authorization vulnerability in myCred myCred mycred allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects myCred: from n/a through 4.0.3.CVSS4.3MediumRoutineCVE-2026-127201wpinsider-1 · simple membership wp user importSimple Membership WP user Import <= 1.9.2 - Cross-Site Request Forgery to add_selective ActionThe Simple Membership WP user Import plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.9.2 This is due to missing or incorrect nonce validation on the add function. This makes it possible for unauthenticated attackers to import arbitrary WordPress users into Simple Membership and modify their WordPress role via the plugin's membership-level-to-role mapping via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.CVSS4.3Medium