CVE-2025-64283

RTMKit <= 1.6.7 - Authenticated (Contributor+) Insecure Direct Object Reference

2025-02-14 00:00

Strategic Overview

Status: Patched in 1.6.8
Affected Plugin: RTMKit
Affected Version: <= 1.6.7
CVSS: 4.3Medium
Weakness type: CWE-639 · Authorization Bypass Through User-Controlled Key
CVE: CVE-2025-64283

At a glance

CVE-2025-64283 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the RTMKit WordPress plugin, affecting versions <= 1.6.7. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 1.6.8; sites on affected versions should update now. Disclosed February 2025, reported by Chazz Wolcott.

Vulnerability Overview

The RTMKit plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.6.7 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Contributor-level access and above, to perform an unauthorized action.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in RTMKit <= 1.6.7 takes an account at Contributor level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For RTMKit the fix is 1.6.8: builds <= 1.6.7 are affected, anything from 1.6.8 onward is not.

Remediation

Update to version 1.6.8, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: RTMKit 1.6.8 closes this, and updating the plugin is the step that ends it.

Login Security
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-64283 https://www.wordfence.com/threat-intel/vulnerabilities/id/d8582985-ce9c-49f2-a7c6-180117e3da28 https://nvd.nist.gov/vuln/detail/CVE-2025-64283

Related records

Same weakness class

4.3CVE-2026-12906: RTMKit Addons for Elementor Information ExposureCVE-2026-12906

Other vulnerabilities in RTMKit

CVSS Vector

4.3

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/