CVE-2026-5149
Deferred Deferred - Pending Action

Incorrect Authorization in RTMKit WordPress Plugin

Vulnerability report for CVE-2026-5149, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-16

Last updated on: 2026-06-16

Assigner: Wordfence

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-16
Last Modified
2026-06-16
Generated
2026-07-06
AI Q&A
2026-06-16
EPSS Evaluated
2026-07-05
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
rtmkit rtmkit to 2.0.7 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The RTMKit plugin for WordPress has a vulnerability in its get_submission_content AJAX endpoint. This endpoint does not properly check if a user has the right permissions to access form submission data. As a result, any authenticated user with Contributor-level access or higher can view form submissions that belong to other users by changing the entries_id parameter.

Impact Analysis

This vulnerability allows attackers with Contributor-level access or above to view arbitrary form submissions from other users without authorization. This can lead to unauthorized disclosure of potentially sensitive or private information submitted through forms on the affected WordPress site.

Compliance Impact

The vulnerability allows authenticated users with Contributor-level access and above to view arbitrary form submissions from other users without proper authorization checks.

This unauthorized access to potentially sensitive form submission data could lead to violations of data protection regulations such as GDPR and HIPAA, which require strict controls on access to personal and sensitive information.

Therefore, exploitation of this vulnerability may result in non-compliance with these common standards and regulations due to improper authorization and potential data exposure.

Detection Guidance

This vulnerability involves the get_submission_content AJAX endpoint in the RTMKit WordPress plugin lacking proper authorization checks. Detection can focus on monitoring HTTP requests to this endpoint, especially those that include the entries_id parameter being iterated or accessed by users with Contributor-level access or higher.

You can detect potential exploitation attempts by examining web server logs or using network monitoring tools to identify repeated or unusual requests to the get_submission_content endpoint.

  • Use command-line tools like curl or wget to test access to the endpoint with different entries_id values and observe if unauthorized data is returned.
  • Example curl command to test access (replace URL and entries_id accordingly):
  • curl -X POST https://yourwordpresssite.com/wp-admin/admin-ajax.php -d 'action=get_submission_content&entries_id=1' -b cookies.txt
  • Check web server logs for repeated access patterns to admin-ajax.php with action=get_submission_content and varying entries_id parameters.
Mitigation Strategies

To mitigate this vulnerability immediately, update the RTMKit plugin to a version later than 2.0.7 where the authorization check issue is fixed.

If an update is not immediately available, restrict access to the get_submission_content AJAX endpoint by limiting it to trusted users or roles, or by implementing additional access controls at the web server or application level.

Additionally, monitor logs for suspicious activity related to this endpoint and consider temporarily disabling the plugin if feasible until a patch is applied.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-5149. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart