{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-10233 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-10233 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-10233 is a high-severity vulnerability in n/a, published on 23 Apr 2018. 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-2018-10233 and fix it if it is affected.\n\nWhat it is: CVE-2018-10233 is a high-severity vulnerability in n/a, published on 23 Apr 2018. 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-2018-10233 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2018-10233/ (Markdown: https://insights.sbomify.com/CVE-2018-10233/index.md)","id":"CVE-2018-10233","markdown":"https://insights.sbomify.com/CVE-2018-10233/index.md","name":"CVE-2018-10233","record":{"aliases":["GHSA-256p-jvfp-85c5"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["account_takeover","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"The User Profile \u0026 Membership WordPress plugin lacks CSRF protections, allowing attackers to force users to perform unintended actions.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"user_profile_\\\u0026_membership","vendor":"ultimatemember"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The User Profile \u0026 Membership plugin before 2.0.7 for WordPress has no mitigations implemented against cross site request forgery attacks. This is a structural finding throughout the entire plugin.","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":"Cross-site request forgery in n/a","id":"CVE-2018-10233","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-10234"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2018-10232"},"products":["n/a"],"published":"2018-04-23","related":[{"cvss_score":7.5,"headline":"Path traversal in Ultimate Member","id":"CVE-2018-0588","kev_date_added":null,"published":"2018-05-14"},{"cvss_score":4.8,"headline":"Cross-site scripting in n/a","id":"CVE-2018-10234","kev_date_added":null,"published":"2018-04-23"},{"cvss_score":4.3,"headline":"Path traversal in Ultimate Member","id":"CVE-2018-0586","kev_date_added":null,"published":"2018-05-14"},{"cvss_score":4.3,"headline":"File upload in Ultimate Member","id":"CVE-2018-0587","kev_date_added":null,"published":"2018-05-14"},{"cvss_score":4.3,"headline":"Missing authorization in Ultimate Member","id":"CVE-2018-0589","kev_date_added":null,"published":"2018-05-14"},{"cvss_score":4.3,"headline":"Missing authorization in Ultimate Member","id":"CVE-2018-0590","kev_date_added":null,"published":"2018-05-14"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"The User Profile \u0026 Membership WordPress plugin lacks CSRF protections, allowing attackers to force users to perform unintended actions.","url":"https://insights.sbomify.com/CVE-2018-10233/"}