dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-5117

HIGH · 8.8 CVSS v3.1 Published 2025-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 Property plugin for WordPress is vulnerable to Privilege Escalation due to a missing capability check on the use of the property_package_user_role metadata in versions 1.0.5 to 1.0.6. This makes it possible for authenticated attackers, with Author‐level access and above, to elevate their privileges to that of an administrator by creating a package post whose property_package_user_role is set to administrator and then submitting the PayPal registration form.

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 Property plugin for WordPress lacks capability checks when processing the property_package_user_role metadata during PayPal registration. Authenticated users with Author-level access can create a package post with property_package_user_role set to administrator, then submit the PayPal registration form to elevate their privileges to administrator.

MitigationUpdate to a patched version of the Property plugin when available, or disable the plugin until a fix is released. The fix requires adding WordPress capability checks (e.g., current_user_can('manage_options')) before allowing property_package_user_role metadata to set user roles.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify Property plugin is installed
    Navigate to WordPress admin > Plugins and look for a plugin named 'Property' or similar real estate/property management plugin. Alternatively, check the wp-content/plugins directory for property-related folders.
    Affected if The Property plugin is installed and active in WordPress
  2. Confirm PayPal registration is enabled
    Check plugin settings or look for PayPal-related functionality in the WordPress admin panel under the Property plugin settings. Look for any configuration related to user registration via PayPal.
    Affected if PayPal registration or payment integration is enabled in the Property plugin settings
  3. Inspect for package posts with elevated role metadata
    Query the WordPress database: SELECT * FROM wp_postmeta WHERE meta_key = 'property_package_user_role' AND meta_value = 'administrator'. Or use a plugin like WP Data Access or phpMyAdmin to search postmeta for this key.
    Affected if Any post exists with property_package_user_role metadata set to 'administrator' or other elevated roles
  4. Review Author-level user capabilities
    Check WordPress users with Author role at Users > All Users. Look for any Author users who unexpectedly have manage_options capability or administrator-level access. Query: SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%administrator%'.
    Affected if Any user with Author role has administrator-level capabilities or access they should not possess
  5. Check for recent package post creations
    Review the Posts or Custom Post Types section for any 'package' post type created recently. Look for posts with property_package_user_role metadata set, especially if created by non-administrator users.
    Affected if Package posts with property_package_user_role metadata exist, created by users without administrator privileges

Your environment is affected if the Property plugin is installed with PayPal registration enabled AND any package posts contain property_package_user_role metadata set to administrator, OR if Author-level users have unexpected administrator capabilities.

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 to a patched version of the Property plugin when available, or disable the plugin until a fix is released. The fix requires adding WordPress capability checks (e.g., current_user_can('manage_options')) before allowing property_package_user_role metadata to set user roles.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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