CVE-2026-97642 man4toman CVE debrief

Who should care

Defenders responsible for WordPress deployments using the Wp Parsidate plugin should assess exposure and prioritize verification and potential updates. This includes reviewing the plugin version, assessing the impact of the vulnerability, and implementing additional monitoring for potential exploitation attempts. Security teams and vulnerability management teams should also review the vulnerability and implement compensating controls for exposed systems.

Why it matters

The CVE-2026-97642 vulnerability in the Wp Parsidate plugin for WordPress allows for Stored Cross-Site Scripting, enabling authenticated attackers to inject arbitrary web scripts. Defenders should assess exposure, prioritize verification and potential updates, and implement additional monitoring for potential exploitation attempts.

• Authenticated attackers with Contributor-level access and above can inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
• The vulnerability allows for Stored Cross-Site Scripting, which can lead to unauthorized script execution on affected pages.
• Defenders should verify the version of the Wp Parsidate plugin in use and update to a version beyond 6.4 if available.
• The vulnerability requires verification of the plugin version and potential updates to prevent exploitation.

Technical summary

The Wp Parsidate plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the calendar Gutenberg block's 'theme' attribute in versions up to, and including, 6.4. This is due to insufficient input sanitization and output escaping on the block attribute value which is concatenated directly into an HTML class attribute in the printCalendar() function without esc_attr(). The vulnerability requires verification of the plugin version and potential updates to prevent exploitation. Defenders should assess exposure and prioritize verification and potential updates.

Defensive priority

Defenders should prioritize verifying and updating the Wp Parsidate plugin to a version beyond 6.4 if available, and assess exposure in their WordPress deployments.

Recommended defensive actions

• Verify and update the Wp Parsidate plugin to a version beyond 6.4 if available
• Assess exposure in WordPress deployments using the Wp Parsidate plugin
• Implement additional monitoring for potential exploitation attempts
• 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 on the vulnerability in the Wp Parsidate plugin for WordPress, including the affected version and the nature of the vulnerability. Defenders should verify the plugin version and review source references for additional context. The CalendarBlock.php and Calendar.php files in the plugin are relevant to understanding the vulnerability.

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.