dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-15369

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Xpro Addons — 140+ Widgets for Elementor plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the get_content_editor function in all versions up to, and including, 1.5.0. This makes it possible for unauthenticated attackers to create published Xpro templates.

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 Xpro Addons plugin for WordPress has a broken access control vulnerability in the get_content_editor function. Unauthenticated attackers can exploit this to create and publish Xpro templates directly, bypassing all authentication and authorization checks.

MitigationUpdate to version 1.5.1 or later which includes the missing capability check. Until the update is applied, consider restricting access to the affected endpoint via web server configuration or temporarily disabling 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Check installed Xpro Addons version
    Navigate to WordPress Admin > Plugins > Installed Plugins > Xpro Addons and note the version number displayed, or inspect the plugin main file header for the Version field
    Affected if The installed version is lower than 1.5.1 or the version cannot be determined (unknown/legacy install)
  2. Verify the get_content_editor function is exposed
    Search the plugin files for the function get_content_editor and examine its capability check (or lack thereof). Look for AJAX action hooks or direct URL endpoints that call this function
    Affected if The function exists and lacks a current_user_can() or similar capability verification check before executing
  3. Test unauthenticated access to the endpoint
    Send a crafted request to the AJAX endpoint or REST API route associated with get_content_editor without providing authentication credentials. Inspect the response to confirm the function executes rather than returning an authentication error
    Affected if The request completes successfully without returning a permission denied or authentication required error
  4. Check for unauthorized Xpro templates in the database
    Query the WordPress database (wp_posts table with post_type containing 'xpro' or 'template') to identify any templates created timestamps that do not correspond to known admin user activity
    Affected if Templates exist that were created by unknown users or at times when no administrator was logged in

You are affected if the installed Xpro Addons version is below 1.5.1 AND the get_content_editor function is accessible without authentication.

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 to version 1.5.1 or later which includes the missing capability check. Until the update is applied, consider restricting access to the affected endpoint via web server configuration or temporarily disabling the plugin.

Recommended fix Moderate confidence

Version 1.5.1 or later (verify current latest release on wordpress.org)

  1. 1. Update the Xpro Addons — 140+ Widgets for Elementor plugin to the latest available version immediately.
  2. 2. After updating, verify that unauthorized users can no longer access the get_content_editor function.
  3. 3. Check existing Xpro templates for any unauthorized changes or additions and remove any suspicious content.
  4. 4. Consider reviewing user access logs around the time of discovery to identify potential exploitation.

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

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-2025-15369 — 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-2025-15369 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