CVE-2023-54358 Adivaha CVE debrief

Who should care

Defenders responsible for WordPress installations with the adivaha Travel Plugin 2.3 should assess exposure and prioritize verification and remediation efforts. This includes reviewing the plugin version, restricting access to the /mobile-app/v3/ endpoint, and monitoring for suspicious activity. Additionally, defenders should consider implementing compensating controls for exposed systems and tracking exceptions and retesting remediated assets.

Why it matters

CVE-2023-54358 is a reflected cross-site scripting vulnerability in the WordPress adivaha Travel Plugin 2.3. Defenders should prioritize verifying and updating the plugin to prevent exploitation, as it allows unauthenticated attackers to inject malicious scripts.

• Potential injection of malicious scripts in victims' browsers
• Possible theft of session tokens or credentials
• Required verification of plugin version and exposure
• Potential impact on web application security

Technical summary

The adivaha Travel Plugin 2.3 for WordPress contains a reflected cross-site scripting vulnerability. An unauthenticated attacker can inject malicious scripts by manipulating the isMobile parameter at the /mobile-app/v3/ endpoint. This vulnerability can lead to the execution of arbitrary code in victims' browsers, potentially resulting in the theft of session tokens or credentials. The vulnerability has a CVSS score of 5.1 and a severity of MEDIUM. Defenders should prioritize verifying and updating the plugin to prevent exploitation.

Defensive priority

Defenders should prioritize verifying and updating the adivaha Travel Plugin to prevent exploitation of this vulnerability.

Recommended defensive actions

• Verify the adivaha Travel Plugin version and update to a fixed version if available.
• Restrict access to the /mobile-app/v3/ endpoint.
• Monitor for suspicious activity and implement additional security measures to detect potential exploitation.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide details about the vulnerability, but the corpus lacks information on affected versions and remediation. The vulnerability was disclosed on 2026-04-09T21:16:04.960Z. The NVD entry and CVE record are the primary sources of information. Defenders should verify the plugin version and exposure, and update to a fixed version if available.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.