{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-5924 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-5924 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-5924 is a medium-severity vulnerability in skywaveinfo WP Firebase Push Notification, published on 4 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-5924 and fix it if it is affected.\n\nWhat it is: CVE-2025-5924 is a medium-severity vulnerability in skywaveinfo WP Firebase Push Notification, published on 4 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-5924 in the wild and no public exploit code.\n\nAffected product: skywaveinfo WP Firebase Push Notification. 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-5924/ (Markdown: https://insights.sbomify.com/CVE-2025-5924/index.md)","id":"CVE-2025-5924","markdown":"https://insights.sbomify.com/CVE-2025-5924/index.md","name":"CVE-2025-5924","record":{"aliases":["GHSA-r38w-4m3x-pjf7"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can trick administrators into sending broadcast notifications via forged requests in the WP Firebase Push Notification plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wp_firebase_push_notification","vendor":"skywavesolutions"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The WP Firebase Push Notification plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2.0. This is due to missing or incorrect nonce validation on the wfpn_brodcast_notification_message() function. This makes it possible for unauthenticated attackers to send broadcast notifications via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.","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":"WP Firebase Push Notification \u003c= 1.2.0 - Cross-Site Request Forgery to Broadcast Notification","id":"CVE-2025-5924","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Bunny’s Print CSS \u003c= 0.95 - Cross-Site Request Forgery to Settings Update","id":"CVE-2025-5925"},"packages":[],"prev":{"headline":"Game Review Block \u003c= 4.8.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via className Parameter","id":"CVE-2025-5923"},"products":["WP Firebase Push Notification"],"published":"2025-07-04","related":[],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["skywaveinfo"]},"summary":"Unauthenticated attackers can trick administrators into sending broadcast notifications via forged requests in the WP Firebase Push Notification plugin.","url":"https://insights.sbomify.com/CVE-2025-5924/"}