CVE-2026-103425 masaakitanaka CVE debrief

Who should care

Defenders responsible for WordPress installations, particularly those with contributor-level access and above, should assess exposure and prioritize verification and remediation. This includes reviewing affected versions, verifying the presence of the vulnerability, and applying patches or updates. Security teams and vulnerability management teams should also review this vulnerability for potential impact on their environments.

Why it matters

The Booking Package plugin for WordPress is vulnerable to Stored Cross-Site Scripting, allowing authenticated attackers to inject arbitrary web scripts, which can execute when a user accesses an injected page. Defenders should prioritize verifying the presence of this vulnerability in their WordPress installations, particularly for contributor-level access and above, and apply patches or updates to affected versions.

• Authenticated attackers with contributor-level access and above can inject arbitrary web scripts
• Injected scripts execute whenever a user accesses an injected page
• Defenders must verify the presence of this vulnerability in their WordPress installations
• Remediation priority is high for affected versions

Technical summary

The Booking Package plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'id' parameter in all versions up to, and including, 1.7.29 due to insufficient input sanitization and output escaping. This allows authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts that execute when a user accesses an injected page. Affected product deployments should be verified, and patches or updates applied to mitigate this vulnerability. Technical details are based on CVE Program and NVD information.

Defensive priority

Defenders should prioritize verifying the presence of this vulnerability in their WordPress installations and assess exposure, particularly for contributor-level access and above.

Recommended defensive actions

• Verify the presence of this vulnerability in WordPress installations
• Assess exposure, particularly for contributor-level access and above
• Apply patches or updates to affected versions
• 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 source item provide details on the vulnerability, including its description, CVSS score, and affected versions. Defenders should verify the presence of this vulnerability in their WordPress installations, particularly for contributor-level access and above, and apply patches or updates to affected versions. Evidence is limited to CVE Program and NVD details. Additional verification is recommended.

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.