dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-6190

HIGH · 8.8 CVSS v3.1 Published 2025-07-23
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 Realty Portal – Agent plugin for WordPress is vulnerable to Privilege Escalation due to missing authorization within the rp_user_profile() AJAX handler in versions 0.1.0 through 0.3.9. The handler reads the client-supplied meta key and value pairs from $_POST and passes them directly to update_user_meta() without restricting to a safe whitelist. This makes it possible for authenticated attackers, with Subscriber-level access and above, to overwrite the wp_capabilities meta and grant themselves the administrator role.

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 Realty Portal – Agent plugin for WordPress contains a privilege escalation vulnerability in versions 0.3.9 and earlier. The rp_user_profile() AJAX handler reads meta key-value pairs directly from $_POST and passes them to update_user_meta() without any authorization checks or input validation. An attacker with Subscriber-level access can supply wp_capabilities as a meta key and a serialized administrator role value to grant themselves full administrative privileges.

MitigationAdd nonce verification and capability checks before processing the AJAX request, and implement a strict whitelist of allowed meta keys that excludes sensitive fields like wp_capabilities.

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 Realty Portal - Agent plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Realty Portal - Agent' or check the plugin directory for /wp-content/plugins/realty-portal-agent/
    Affected if Plugin is installed and version is 0.3.9 or earlier (version number found in plugin header or readme.txt)
  2. Confirm the vulnerable AJAX handler exists
    Search plugin PHP files for 'rp_user_profile' and 'wp_ajax_rp_user_profile' to verify the AJAX action is registered
    Affected if The function rp_user_profile is registered as a WordPress AJAX hook without capability checks
  3. Check for subscriber-level user accounts
    In WordPress admin, go to Users and look for any accounts with the Subscriber role, or query the wp_usermeta table for wp_capabilities containing 'subscriber'
    Affected if At least one Subscriber-level user account exists in the system
  4. Verify no meta key whitelist is implemented
    Examine the rp_user_profile() function in the plugin code to see if meta keys are whitelisted before passing to update_user_meta()
    Affected if The code directly passes $_POST meta keys to update_user_meta() without validating against an allowed list that excludes wp_capabilities

A user is affected if the Realty Portal - Agent plugin version 0.3.9 or earlier is installed, the rp_user_profile AJAX handler is active, and any Subscriber-level accounts exist on the site.

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

Add nonce verification and capability checks before processing the AJAX request, and implement a strict whitelist of allowed meta keys that excludes sensitive fields like wp_capabilities.

Recommended fix High confidence

0.3.10 or later

  1. Update the Realty Portal – Agent plugin for WordPress to the latest available version from the WordPress plugin repository
  2. Verify the plugin update was applied successfully in the WordPress admin dashboard
  3. Confirm that user capabilities have not been improperly modified by reviewing user roles

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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