{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-4179 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-4179 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-4179 is a high-severity vulnerability in v1rustyle Flynax Bridge, published on 2 May 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-4179 and fix it if it is affected.\n\nWhat it is: CVE-2025-4179 is a high-severity vulnerability in v1rustyle Flynax Bridge, published on 2 May 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-4179 in the wild and no public exploit code.\n\nAffected product: v1rustyle Flynax Bridge. 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-4179/ (Markdown: https://insights.sbomify.com/CVE-2025-4179/index.md)","id":"CVE-2025-4179","markdown":"https://insights.sbomify.com/CVE-2025-4179/index.md","name":"CVE-2025-4179","record":{"aliases":["GHSA-7cm5-6vm2-x739"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can register as authors due to missing capability checks in the Flynax Bridge WordPress plugin.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"flynax_bridge","vendor":"flynax"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The Flynax Bridge plugin for WordPress is vulnerable to limited Privilege Escalation due to a missing capability check on the registerUser() function in all versions up to, and including, 2.2.0. This makes it possible for unauthenticated attackers to register new user accounts as authors.","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":"Flynax Bridge \u003c= 2.2.0 - Unauthenticated Limited Privilege Escalation","id":"CVE-2025-4179","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"PCMan FTP Server TRACE Command buffer overflow","id":"CVE-2025-4180"},"packages":[],"prev":{"headline":"xiaowei1118 java_server File Upload API FoodController.java path traversal","id":"CVE-2025-4178"},"products":["Flynax Bridge"],"published":"2025-05-02","related":[{"cvss_score":9.8,"headline":"Flynax Bridge \u003c= 2.2.0 - Unauthenticated Privilege Escalation via Password Update","id":"CVE-2025-3603","kev_date_added":null,"published":"2025-04-24"},{"cvss_score":9.8,"headline":"Flynax Bridge \u003c= 2.2.0 - Unauthenticated Privilege Escalation via Account Takeover","id":"CVE-2025-3604","kev_date_added":null,"published":"2025-04-24"},{"cvss_score":5.3,"headline":"Flynax Bridge \u003c= 2.2.0 - Unauthenticated Arbitrary User Deletion","id":"CVE-2025-4177","kev_date_added":null,"published":"2025-05-02"}],"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":["v1rustyle"]},"summary":"Unauthenticated attackers can register as authors due to missing capability checks in the Flynax Bridge WordPress plugin.","url":"https://insights.sbomify.com/CVE-2025-4179/"}