pretix Widget WordPress Plugin Vulnerability (CVE-2026-127140)

On this page

Security Alert Summary

The pretix Widget WordPress Plugin contains a server-side request forgery (SSRF) risk that can result in response bodies being stored publicly on the WordPress site. The plugin pre-fetches CSS and JS into a local cache using wp_remote_get instead of the safer wp_safe_remote_get. Exploitation requires WordPress permissions sufficient to create or modify pages.


CVE Details

  • CVE ID: CVE-2026-127140
  • Affected component: pretix Widget WordPress Plugin
  • Affected versions: versions less than 1.1.2
  • Published: November 17, 2026 at 1:17:33 PM UTC
  • Last modified: November 17, 2026 at 1:17:33 PM UTC
  • CVSS (version 4.0) base score: 3.8 (LOW)
  • CVSS vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
  • Authentication / requirements: Attack requirements: PRESENT
  • Privileges required: LOW (requires an account with permissions to create or modify pages)
  • User interaction: NONE
  • Primary impact: Confidentiality: HIGH; Integrity: NONE; Availability: NONE
  • Weakness (CWE): CWE-918

Technical Details

The plugin pre-fetches external CSS and JavaScript files into a local cache and stores those cached resources publicly on the WordPress instance. These HTTP calls are made with the WordPress HTTP function wp_remote_get rather than wp_safe_remote_get. Because wp_remote_get does not include the same safety checks, an attacker with the ability to create or modify pages can supply URLs that trigger server-side request forgery (SSRF) and cause the plugin to retrieve arbitrary URLs. The vulnerability description specifically notes SSRF with body extraction, meaning response bodies fetched by the plugin can be written into the public cache on the site.

The impact is limited by the requirement for a user account with page creation or modification privileges; it does not, based on the provided data, indicate unauthenticated remote code execution or direct modification of core site data beyond the cached responses.


How This Could Impact Your Website

Consider a scenario where a site owner delegates content updates to an internal staff member and an external contractor. If a user with permission to add or edit pages includes or configures the pretix Widget with a crafted URL, the plugin may fetch internal endpoints or other internal resources and store the response bodies publicly. This can lead to exposure of internal data or service responses, which in turn may reveal internal email addresses or other sensitive information and increase the risk of targeted phishing or social engineering against staff or contractors. If you are unsure whether your site is affected or how to assess your current user roles and plugins, it may be worth having a professional review.


Recommended Actions

  • Update the affected plugin as soon as a patched version is available.
  • Review and reduce unnecessary user roles, especially contributor or editor accounts that can create or modify pages.
  • Enforce strong passwords and enable two-factor authentication for editors and administrators.
  • Remove unused or unmaintained plugins from the site.
  • Monitor site activity and cached content for unusual behavior or unexpected publicly stored responses.

If youd like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.


References