Findings

Vulnerability · CVE-2025-11924

ninjaforms ninja_forms Authorization Bypass Through User-Controlled Key

Published Dec 17, 2025 · corrected/updated Dec 17, 2025 · ninjaforms ninja_forms · evidence confidence very high

The Ninja Forms – The Contact Form Builder That Grows With You plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 3.13.2. This is due to the plugin not properly verifying that a user is authorized before the REST endpoints return form metadata and submission content. This makes it possible for unauthenticated attackers to read arbitrary form definitions and submission records via a leaked bearer token granted they can load any page containing the Submissions Table block. NOTE: The developer released a patch for this issue in 3.13.1, but ina

Grounded briefings

Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.

Executive

CVE-2025-11924 is a unknown public vulnerability record for ninjaforms ninja_forms. CISA lists it as known exploited. Published remediation guidance: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.

System administrator

Identify whether ninjaforms ninja_forms is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: ninjaforms ninja_forms. Published remediation guidance: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.

Security analyst

Signals on file: no CVSS/EPSS yet. CISA lists it as known exploited. Sources contributing to this record: cve_org, vulncheck_kev. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.

Exploitation and remediation

  • Exploitation evidence

    Confirmed in CISA KEV since Dec 17, 2025. Listed in CISA KEV and VulnCheck KEV.

  • Patch and remediation

    Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

  • Safe detection guidance

    Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.

Technology hubs

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Dec 17, 2025 · VulnCheck KEV

    Detected

    The Ninja Forms – The Contact Form Builder That Grows With You plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 3.13.2. This is due to the plugin not properly verifying that a user is authorized before the REST endpoints return form metadata and submission content. This makes it possible for unauthenticated attackers to read arbitrary form de

  2. Dec 17, 2025 · CISA KEV

    Known exploited

    Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

Affected

  • vendor ninjaforms ninja_formsversion unspecified

Sources

  • CVE.orgVulnerability recordCVE-2025-11924

    Official CVE identifier

    cve.org
  • VulnCheck KEVConfirmed exploitationCVE-2025-11924

    The Ninja Forms – The Contact Form Builder That Grows With You plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 3.13.2. This is due to the plugin not properly verifying that a user is authorized before the REST endpoints ret

    vulncheck.com

References