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

> 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.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2026
- **Updated:** 13 Apr 2026
- **Also known as:** GHSA-cfc8-rw2h-jfg7

## What is CVE-2026-4979?

CVE-2026-4979 is a medium-severity server-side request forgery vulnerability in stiofansisland UsersWP – Front-end login form, User Registration, User Profile & 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.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-4979?


## How do I fix CVE-2026-4979?

No fix has been published for CVE-2026-4979 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-4979 being exploited?

There is no known exploitation of CVE-2026-4979 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4979 and fix it if it is affected.

What 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 & 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.
Exploitation: There is no known exploitation of CVE-2026-4979 in the wild and no public exploit code.

Affected product: stiofansisland UsersWP – Front-end login form, User Registration, User Profile & Members Directory plugin for WP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-4979/ (Markdown: https://insights.sbomify.com/CVE-2026-4979/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4979
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4979
- OSV: https://osv.dev/vulnerability/CVE-2026-4979

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-4979/
Summaries are generated and may contain mistakes; the official description above is the record.