CVE-2026-65050 Saturday Drive CVE debrief

Who should care

Defenders responsible for WordPress installations with the Ninja Forms plugin should assess the exposure of sensitive form submissions and prioritize remediation. This includes verifying the presence of the vulnerable plugin version, reviewing compensating controls, and monitoring for potential exploitation attempts. Security teams and vulnerability management teams should also review the affected scope and severity to ensure proper remediation and risk

Why it matters

The CVE-2026-65050 vulnerability in the Ninja Forms WordPress plugin allows authenticated attackers to expose stored form submissions to unauthenticated visitors, potentially leading to the disclosure of sensitive information.

• Authenticated attackers with Author-level privileges can expose stored form submissions to unauthenticated visitors.
• Sensitive form submission field values, including personally identifiable information, can be accessed by unauthenticated visitors.
• Defenders need to verify the presence of this vulnerability in their WordPress installations and assess the exposure of sensitive form submissions.
• Remediation priority is high due to the potential exposure of sensitive information.

Technical summary

The Ninja Forms WordPress plugin version 3.14.8 and prior contains a missing authorization vulnerability in the render callback of the `ninja-forms/submissions-table` Gutenberg block. This allows authenticated attackers with Author-level privileges to expose stored form submissions to unauthenticated visitors by embedding the block with an arbitrary formID on a published post. Attackers can retrieve the signed bearer token injected into every page visitor's browser via `wp_localize_script` and use it against the REST API submissions endpoint to access all saved form submission field values, including sensitive personally identifiable information such as names, email addresses, and phone numbers. Defenders need

Defensive priority

Defenders should prioritize verifying the presence of this vulnerability in their WordPress installations and assess the exposure of sensitive form submissions.

Recommended defensive actions

• Verify the presence of the Ninja Forms WordPress plugin version 3.14.8 or prior in your WordPress installation.
• Assess the exposure of sensitive form submissions and prioritize remediation.
• Monitor for potential exploitation attempts and update the plugin to a fixed version if available.
• 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, including its description, CVSS score, and affected versions. However, the exact versions affected and the remediation steps are not explicitly stated.

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.