Hostel Plugin Vulnerability (CVE-2026-1645)

On this page

Security Alert Summary

The Hostel plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in the custom_currency parameter and the locale_url setting. Authenticated attackers with Administrator-level access can inject scripts that execute when a user views an injected page. The issue is present in multi-site installations and in installations where unfiltered_html has been disabled.

CVE Details

  • CVE ID: CVE-2026-1645
  • Affected component: Hostel plugin for WordPress
  • Affected versions: all versions up to and including 1.1.8
  • Published: September 22, 2026 at 8:16:39 AM UTC
  • Last modified: September 22, 2026 at 3:17:09 PM UTC
  • CVSS v3.1: Base Score 4.4, MEDIUM — Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N
  • Authentication / privileges / user interaction: Requires authenticated user with high privileges (Administrator-level) — Privileges Required: HIGH; User Interaction: NONE; Attack Vector: NETWORK; Attack Complexity: HIGH
  • Primary impact: Confidentiality: LOW; Integrity: LOW; Availability: NONE
  • Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation – Cross-site Scripting)

Technical Details

The vulnerability is a stored cross-site scripting (XSS) issue caused by insufficient input sanitization and output escaping for two fields: the custom_currency parameter and the locale_url setting. When a user with Administrator-level privileges supplies crafted input for these fields, the plugin may persist the input and later output it into pages without proper escaping, allowing injected JavaScript to execute in the browser of any user who views the affected page.

The issue only manifests in multi-site configurations and in sites where the unfiltered_html capability has been disabled, which affects the contexts where HTML input is filtered and stored. The CVSS vector indicates that exploitation requires high privileges and is not dependent on user interaction; the attack complexity is high and the overall impacts are limited to confidentiality and integrity at a low level.

How This Could Impact Your Website

In a realistic scenario, an organization runs a multi-site WordPress network where administrators and editors manage listings or content. An attacker with Administrator-level access could insert a malicious payload into the custom_currency or locale_url fields. When other users, such as site editors, contributors, or external contractors, visit the injected page, the script can execute in their browsers. Practical consequences include limited disclosure of data visible to the browser and manipulation of page content or forms, increasing the risk of targeted phishing or social engineering against internal staff.

If you’re 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 administrative accounts and contributor roles.
  • Enforce strong passwords and two-factor authentication for editors and administrators.
  • Remove unused or unmaintained plugins from your installation.
  • Monitor site activity and logs for unusual behavior, such as unexpected changes to settings or content.

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


References