Live › vulnerability › CVE-2026-103480
Go to dashboardThe Tourfic WordPress plugin up to and including 3.0.1 fails to escape the 'type' parameter, so an authenticated contributor can store JavaScript that runs when any visitor opens the affected page. The payload can run in the browser of guests and logged-in users, which may let an attacker act as them on the site.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Sites running the Tourfic plugin at version 3.0.1 or lower where contributor-level accounts can create or edit content. Sites without the plugin, or with no contributor or higher accounts that other people can use, are at much lower risk. Stored XSS needs a user to load the injected page, so public-facing booking pages are the main concern.
No product ranges from the sources yet.
wp plugin get tourfic --field=version3.0.1 or lower3.0.1 (the sources do not name the fixed version; check the plugin changelog)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The Tourfic – AI Powered Travel Booking, Hotel Booking & Car Rental plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'type' parameter in all versions up to, and including, 3.0.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The wp_kses_post filter applied on save does not strip the payload because angle-bracket characters are not required, allowing the unescaped attribute value to survive storage and fire as a live event handler in the unauthenticated (guest) rendering branch.
This page as .md · .json · in your agent: get_signal("CVE-2026-103480")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.