CVE-2026-1934

NVD	https://nvd.nist.gov/vuln/detail/CVE-2026-1934
CWE	https://cwe.mitre.org/data/definitions/862.html

The Motors – Car Dealership & Classified Listings plugin for WordPress is vulnerable to Payment Bypass via insecure user meta update in all versions up to, and including, 1.4.103 This is due to the stm_save_user_extra_fields() function updating sensitive user meta fields from POST data without verifying that the current user should have permission to modify those fields. The function hooks into the personal_options_update action and only checks current_user_can(edit_user, $user_id), which passes for any user editing their own profile. This makes it possible for authenticated attackers, with Subscriber-level access and above, to set their stm_payment_status to completed, bypassing the PayPal payment verification and gaining access to paid Dealer membership features without completing any transaction.

Weakness

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Potential Mitigations

Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries.
Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.
One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.

https://cwe.mitre.org/data/definitions/665.html

Missing Authorization

Weakness

Potential Mitigations

References

CVE-2026-1934

Missing Authorization

Weakness

Potential Mitigations

Related Attack Patterns

References