# CVE-2024-1519: Cross-site scripting in Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress

> Unauthenticated attackers can inject arbitrary scripts via the name parameter in ProfilePress, requiring an active member listing page and Gerbera theme.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-qq82-99vq-37qp

## What is CVE-2024-1519?

CVE-2024-1519 is a medium-severity cross-site scripting vulnerability in properfraction Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress, published on 20 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'name' parameter in all versions up to, and including, 4.14.4 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires a member listing page to be active and using the Gerbera theme.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2024-1519?

It affects 1 product.


Products: Properfraction Profilepress.

## How do I fix CVE-2024-1519?

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

## Is CVE-2024-1519 being exploited?

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

## Other vulnerabilities in properfraction Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress

- [CVE-2021-34621](https://insights.sbomify.com/CVE-2021-34621/): ProfilePress 3.0 - 3.1.3 - Unauthenticated Privilege Escalation (critical 9.8)
- [CVE-2021-34622](https://insights.sbomify.com/CVE-2021-34622/): ProfilePress 3.0 - 3.1.3 - Authenticated Privilege Escalation (critical 9.8)
- [CVE-2021-34623](https://insights.sbomify.com/CVE-2021-34623/): ProfilePress 3.0 - 3.1.3 - Arbitrary File Upload in Image Uploader Component (critical 9.8)
- [CVE-2021-34624](https://insights.sbomify.com/CVE-2021-34624/): ProfilePress 3.0 - 3.1.3 - Arbitrary File Upload in File Uploader Component (critical 9.8)
- [CVE-2023-41954](https://insights.sbomify.com/CVE-2023-41954/): WordPress ProfilePress plugin <= 4.13.1 - Unauthenticated Limited Privilege Escalation vulnerability (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1519 and fix it if it is affected.

What it is: CVE-2024-1519 is a medium-severity cross-site scripting vulnerability in properfraction Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress, published on 20 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-1519 in the wild and no public exploit code.

Affected product: properfraction Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress. 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-2024-1519/ (Markdown: https://insights.sbomify.com/CVE-2024-1519/index.md)
```

## Sources

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

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