RTMKit: A security weakness
RTMKit is affected by a security weakness. Exploitation requires an authenticated contributor account. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 2.0.7.
- Component
- RTMKit
- Plugin slug
rometheme-for-elementor- Affected
- <= 2.0.7
- Safe version
- See mitigation notes
- Published
- Jun 16, 2026
This CVE was published Jun 16, 2026 and is one of 18 known issues for this plugin.
Update, patch or deactivate.
No fixed release is identified. Update RTMKit when a release after 2.0.7 becomes available; until then, disable and remove it when the site's risk warrants. The official upstream changelog lists version 2.1.2, which is newer than the published affected range. Its changelog does not clearly confirm this specific fix, so it is not counted as a known-safe release.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The RTMKit plugin for WordPress is vulnerable to Incorrect Authorization in all versions up to, and including, 2.0.7 This is due to the get_submission_content AJAX endpoint lacking a capability check to verify that a user has permission to access the requested form submission data. This makes it possible for authenticated attackers, with Contributor-level access and above, to view arbitrary form submissions from other users by iterating the entries_id parameter.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N