dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2025-4631

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 Profitori plugin for WordPress is vulnerable to Privilege Escalation due to a missing capability check on the stocktend_object endpoint in versions 2.0.6.0 to 2.1.1.3. This makes it possible to trigger the save_object_as_user() function for objects whose '_datatype' is set to 'users',. This allows unauthenticated attackers to write arbitrary strings straight into the user’s wp_capabilities meta field, potentially elevating the privileges of an existing user account or a newly created one to that of an administrator.

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 Profitori WordPress plugin (versions 2.0.6.0 to 2.1.1.3) has a critical privilege escalation vulnerability where the stocktend_object AJAX endpoint lacks capability checks. Unauthenticated attackers can trigger the save_object_as_user() function with _datatype set to 'users', allowing direct modification of the wp_capabilities meta field to grant administrator privileges to any user account.

MitigationUpdate to the latest version of Profitori if a patch is available; otherwise disable the plugin. Consider applying a WAF rule to block access to the vulnerable stocktend_object endpoint until a fix is deployed.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm Profitori plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Profitori' in the list. Note the installed version displayed.
    Affected if The Profitori plugin appears in the installed plugins list with a version number visible.
  2. Check plugin version against fixed release
    Compare the installed version to the latest version available in the WordPress plugin repository. The vulnerability exists in versions prior to the patched release.
    Affected if The installed version is older than the version that includes the security fix.
  3. Verify REST API endpoint accessibility
    Make an unauthenticated HTTP request to the endpoint: /wp-json/stocktend/v1/object?_datatype=users - Check if the server returns a valid JSON response rather than a 401/403 authentication error.
    Affected if The endpoint responds to unauthenticated requests without requiring authentication.
  4. Inspect user accounts for unauthorized admin privileges
    In WordPress admin, go to Users > All Users and review all accounts with Administrator role. Cross-reference against expected admin accounts. Check wp_usermeta table for any user with wp_capabilities containing 'administrator' that you did not create.
    Affected if There are administrator accounts present that were not created by known administrators, or unexpected wp_capabilities meta entries exist.

A user is affected if the Profitori plugin is installed and the /wp-json/stocktend/v1/object endpoint accepts unauthenticated requests, allowing unauthorized modification of user 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.

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

Update to the latest version of Profitori if a patch is available; otherwise disable the plugin. Consider applying a WAF rule to block access to the vulnerable stocktend_object endpoint until a fix is deployed.

Recommended fix Moderate confidence

Profitori plugin version 2.1.1.4 or later

  1. 1. Update the Profitori plugin to the latest available version (2.1.1.4 or higher) via the WordPress admin dashboard under Plugins > All Plugins > Profitori > Update Now
  2. 2. Alternatively, update via WordPress.org plugin repository or upload the latest version manually
  3. 3. After updating, verify that the plugin is functioning correctly by checking your product inventory and pricing features
  4. 4. Review user accounts that may have been created or modified during the vulnerability window using the Users panel in WordPress admin

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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