{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-4979 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-4979 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-4979 is a medium-severity server-side request forgery vulnerability in stiofansisland UsersWP – Front-end login form, User Registration, User Profile \u0026 Members Directory plugin for WP, published on 11 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-4979 and fix it if it is affected.\n\nWhat it is: CVE-2026-4979 is a medium-severity server-side request forgery vulnerability in stiofansisland UsersWP – Front-end login form, User Registration, User Profile \u0026 Members Directory plugin for WP, published on 11 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-4979 in the wild and no public exploit code.\n\nAffected product: stiofansisland UsersWP – Front-end login form, User Registration, User Profile \u0026 Members Directory plugin for WP. 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-2026-4979/ (Markdown: https://insights.sbomify.com/CVE-2026-4979/index.md)","id":"CVE-2026-4979","markdown":"https://insights.sbomify.com/CVE-2026-4979/index.md","name":"CVE-2026-4979","record":{"aliases":["GHSA-cfc8-rw2h-jfg7"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated attackers can exploit insufficient URL validation in UsersWP to force the server into making arbitrary HTTP requests, enabling internal network scanning and access to sensitive services.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"The UsersWP – Front-end login form, User Registration, User Profile \u0026 Members Directory plugin for WP plugin for WordPress is vulnerable to blind Server-Side Request Forgery in all versions up to, and including, 1.2.58. This is due to insufficient URL origin validation in the process_image_crop() method when processing avatar/banner image crop operations. The function accepts a user-controlled URL via the uwp_crop POST parameter and only validates it using esc_url() for sanitization and wp_check_filetype() for extension verification, without enforcing that the URL references a local uploads file. The URL is then passed to uwp_resizeThumbnailImage() which uses it in PHP image processing functions (getimagesize(), imagecreatefrom*()) that support URL wrappers and perform outbound HTTP requests. This makes it possible for authenticated attackers with subscriber-level access and above to coerce the WordPress server into making arbitrary HTTP requests to attacker-controlled or internal network destinations, enabling internal network scanning and potential access to sensitive services.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"UsersWP \u003c= 1.2.58 - Authenticated (Subscriber+) Server-Side Request Forgery via 'uwp_crop' Parameter","id":"CVE-2026-4979","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Improper Restriction of XML External Entity Reference in Inkscape","id":"CVE-2026-4980"},"packages":[],"prev":{"headline":"SQLi in UMAI Vision's Traffic Analysis System","id":"CVE-2026-4978"},"products":["UsersWP – Front-end login form, User Registration, User Profile \u0026 Members Directory plugin for WP"],"published":"2026-04-11","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-13","vendors":["stiofansisland"]},"summary":"Authenticated attackers can exploit insufficient URL validation in UsersWP to force the server into making arbitrary HTTP requests, enabling internal network scanning and access to sensitive services.","url":"https://insights.sbomify.com/CVE-2026-4979/"}