dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-41556

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Subscriber Cross Site Scripting (XSS) in ProfilePress <= 4.16.13 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Cross Site Scripting (XSS) vulnerability in ProfilePress WordPress plugin affecting users with Subscriber role privileges. The vulnerability exists in versions up to and including 4.16.13, allowing authenticated low-privilege users to potentially inject malicious scripts.

MitigationUpdate ProfilePress to a version newer than 4.16.13. If immediate update is not possible, consider restricting subscriber registration or implementing additional input sanitization at the web application firewall level.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm ProfilePress plugin is installed
    In WordPress admin dashboard, go to Plugins > Installed Plugins and look for ProfilePress, or check the /wp-content/plugins/ directory for the profilepress folder
    Affected if ProfilePress plugin is present on the WordPress site
  2. Check installed ProfilePress version
    In WordPress admin, go to Plugins > Installed Plugins and find the ProfilePress entry to view the version number, or inspect the main plugin file (e.g., /wp-content/plugins/profilepress/profilepress.php) for the 'Version' header in the plugin comment block
    Affected if Version is 4.16.13 or lower
  3. Verify subscriber user registration is enabled
    In WordPress admin, go to ProfilePress > Settings > General and check if the 'Enable User Registration' or 'Allow Subscriber Registration' option is turned on, or inspect the wp_options table for option_name containing 'pp_enable_registration' or similar
    Affected if Subscriber/user registration functionality is enabled in ProfilePress settings
  4. Check for existing subscriber-level accounts
    In WordPress admin, go to Users > All Users and review the list for users with the 'Subscriber' role, or query the wp_users and wp_usermeta tables where meta_value includes 'subscriber'
    Affected if There are Subscriber role users registered on the site

A site is affected if ProfilePress plugin version 4.16.13 or lower is installed AND subscriber/user registration is enabled, allowing authenticated low-privilege users to potentially exploit the XSS vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update ProfilePress to a version newer than 4.16.13. If immediate update is not possible, consider restricting subscriber registration or implementing additional input sanitization at the web application firewall level.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41556 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41556 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data