{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-14081 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-14081 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-14081 is a medium-severity vulnerability in ultimatemember Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction \u0026 Membership Plugin, published on 17 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-14081 and fix it if it is affected.\n\nWhat it is: CVE-2025-14081 is a medium-severity vulnerability in ultimatemember Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction \u0026 Membership Plugin, published on 17 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-14081 in the wild and no public exploit code.\n\nAffected product: ultimatemember Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction \u0026 Membership Plugin. 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-14081/ (Markdown: https://insights.sbomify.com/CVE-2025-14081/index.md)","id":"CVE-2025-14081","markdown":"https://insights.sbomify.com/CVE-2025-14081/index.md","name":"CVE-2025-14081","record":{"aliases":["GHSA-65hf-c38w-3rrh"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated subscribers can bypass profile privacy restrictions to modify their own profile settings, ignoring administrator-defined role permissions.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"The Ultimate Member plugin for WordPress is vulnerable to Profile Privacy Setting Bypass in all versions up to, and including, 2.11.0. This is due to a flaw in the secure fields mechanism where field keys are stored in the allowed fields list before the `required_perm` check is applied during rendering. This makes it possible for authenticated attackers with Subscriber-level access to modify their profile privacy settings (e.g., setting profile to \"Only me\") via direct parameter manipulation, even when the administrator has explicitly disabled the option for their role.","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":"Ultimate Member \u003c= 2.11.0 - Authenticated (Subscriber+) Profile Privacy Setting Bypass","id":"CVE-2025-14081","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Keycloak Admin REST (Representational State Transfer) API does not properly enforce permissions","id":"CVE-2025-14082"},"packages":[],"prev":{"headline":"Frontend Post Submission Manager Lite \u003c= 1.2.5 - Missing Authorization to Unauthenticated Arbitrary Post Modification","id":"CVE-2025-14080"},"products":["Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction \u0026 Membership Plugin"],"published":"2025-12-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":["ultimatemember"]},"summary":"Authenticated subscribers can bypass profile privacy restrictions to modify their own profile settings, ignoring administrator-defined role permissions.","url":"https://insights.sbomify.com/CVE-2025-14081/"}