{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-11924 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-11924 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-11924 is a high-severity missing authorization vulnerability in Ninjaforms Ninja Forms, published on 17 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-11924 and fix it if it is affected.\n\nWhat it is: CVE-2025-11924 is a high-severity missing authorization vulnerability in Ninjaforms Ninja Forms, published on 17 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-11924 in the wild and no public exploit code.\n\nAffected product: Ninjaforms Ninja Forms. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-11924/ (Markdown: https://insights.sbomify.com/CVE-2025-11924/index.md)","id":"CVE-2025-11924","markdown":"https://insights.sbomify.com/CVE-2025-11924/index.md","name":"CVE-2025-11924","record":{"aliases":["GHSA-377j-r7wx-8v2h"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can read arbitrary form definitions and submission records via leaked bearer tokens due to missing authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"ninja_forms","vendor":"ninjaforms"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"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 `ninja-forms-views` 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 inadvertently introduced a REST API endpoint in which a valid bearer token could be minted for arbitrary form IDs, making this patch ineffective.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Missing authorization in Ninja Forms – The Contact Form Builder That Grows With You","id":"CVE-2025-11924","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ninjaforms:ninja_forms","products":["ninjaforms:ninja_forms"],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Incorrect Content-Type Header","id":"CVE-2025-11925"},"packages":[],"prev":{"headline":"Privilege escalation in LifterLMS – WP LMS for eLearning, Online Courses, \u0026 Quizzes","id":"CVE-2025-11923"},"products":["Ninja Forms – The Contact Form Builder That Grows With You"],"published":"2025-12-17","related":[{"cvss_score":9.8,"headline":"Ninja-forms \u003c 3.11.1 - Unauthenticated PHP Objection","id":"CVE-2025-9083","kev_date_added":null,"published":"2025-09-18"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2016-1209","kev_date_added":null,"published":"2016-05-14"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2018-20981","kev_date_added":null,"published":"2019-08-22"},{"cvss_score":8.8,"headline":"Cross-site request forgery in Ninja Forms","id":"CVE-2024-25572","kev_date_added":null,"published":"2024-04-11"},{"cvss_score":8.8,"headline":"Ninja Forms \u003c 3.4.34 - Authenticated SendWP Plugin Installation and Client Secret Key Disclosure","id":"CVE-2021-24163","kev_date_added":null,"published":"2021-04-05"},{"cvss_score":8.6,"headline":"Other in n/a","id":"CVE-2018-16308","kev_date_added":null,"published":"2018-09-01"},{"cvss_score":7.6,"headline":"WordPress Ninja Forms plugin \u003c= 3.6.25 - Contributor+ Broken Access Control vulnerability","id":"CVE-2023-38386","kev_date_added":null,"published":"2024-06-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["kstover"]},"summary":"Unauthenticated attackers can read arbitrary form definitions and submission records via leaked bearer tokens due to missing authorization checks.","url":"https://insights.sbomify.com/CVE-2025-11924/"}