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

CVE-2026-1559

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

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
The Youzify plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'checkin_place_id' parameter in all versions up to, and including, 1.3.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 · high confidence

The Youzify WordPress plugin fails to properly sanitize the 'checkin_place_id' parameter and escape it during output, allowing authenticated users with Subscriber-level access or higher to inject malicious JavaScript. This stored XSS executes automatically when other users view affected pages.

MitigationUpdate Youzify to the latest version if available, and implement proper input sanitization (sanitize_text_field) and output escaping (esc_attr/esc_html) for the checkin_place_id parameter throughout the plugin.

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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 Youzify plugin is installed
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'Youzify' in the list. Note the installed version from the plugin details.
    Affected if Youzify plugin is active and installed without having applied a patch for CVE-2026-1559
  2. Check for Subscriber-level user accounts
    In WordPress admin, go to Users > All Users. Review the role column to identify any users assigned the 'Subscriber' role.
    Affected if At least one user with Subscriber-level access or higher exists in the WordPress installation
  3. Determine if BuddyPress checkin feature is enabled
    Youzify extends BuddyPress functionality. Check BuddyPress settings at Users > Dashboard > Youzify Settings > Activity > Check-ins tab, or inspect frontend pages for check-in functionality.
    Affected if The checkin feature module is enabled and accessible to subscribers
  4. Inspect the checkin_place_id parameter handling
    If you have access to plugin source code, locate files handling the checkin_place_id parameter (typically in youzify/includes/buddypress/activity or similar directories). Search for the parameter and verify if sanitize_text_field is applied on input and esc_attr/esc_html on output.
    Affected if The checkin_place_id parameter is processed without proper sanitization (sanitize_text_field) and output escaping (esc_attr/esc_html)
  5. Verify stored XSS payload exists in database
    Check the wp_bp_activity_meta table (or equivalent, depending on your prefix) for activity entries where meta_key contains 'checkin_place_id' and the meta_value contains unsanitized script tags or javascript: URIs.
    Affected if Malicious JavaScript payloads are stored in the checkin_place_id metadata without sanitization

You are affected if the Youzify plugin is installed and active, subscribers or higher-privileged users exist, the checkin feature is enabled, and the checkin_place_id parameter lacks proper input sanitization and output escaping.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Youzify to the latest version if available, and implement proper input sanitization (sanitize_text_field) and output escaping (esc_attr/esc_html) for the checkin_place_id parameter throughout the plugin.

Recommended fix Moderate confidence

Youzify plugin version 1.3.7 or latest available version

  1. 1. Log in to WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Youzify plugin in the list
  4. 4. If an update is available, click 'Update Now' to update to the latest version
  5. 5. After updating, verify the plugin version is 1.3.7 or later in the plugins list
  6. 6. Test the functionality related to check-ins and place IDs to confirm the fix does not break existing features

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1559 — 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-1559 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