# CVE-2026-19848: ProfilePress < 4.17.1 - Unauthenticated Arbitrary Shortcode Execution via Display Name

> Unauthenticated attackers can inject shortcodes into profile fields to disclose sensitive user data like email and login dates.

- **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:** 21 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-4v3w-374v-v8px

## What is CVE-2026-19848?

CVE-2026-19848 is a medium-severity code injection vulnerability in Unknown ProfilePress, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ProfilePress WordPress plugin before 4.17.1 does not strip shortcodes from two of its profile fields before rendering them on public pages, allowing unauthenticated attackers to store shortcodes that are then executed when the page is viewed, disclosing a chosen user's email address, login and registration date.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-19848 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19848 is a medium-severity code injection vulnerability in Unknown ProfilePress, published on 21 Aug 2026. 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-2026-19848 in the wild and no public exploit code.

Affected product: Unknown 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-2026-19848/ (Markdown: https://insights.sbomify.com/CVE-2026-19848/index.md)
```

## Sources

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

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