dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-5149

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 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.

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

This is an Insecure Direct Object Reference (IDOR) vulnerability combined with Missing Authorization. The get_submission_content AJAX endpoint in the RTMKit WordPress plugin fails to verify that the requesting user has permission to access the specific form submission before returning data. An authenticated attacker with Contributor-level access can read arbitrary form submissions by manipulating the entries_id parameter.

MitigationAdd a WordPress capability check (e.g., current_user_can()) to the get_submission_content AJAX endpoint to verify the user has appropriate permissions before returning form submission data, and validate that the requested entry belongs to a form the user is authorized to access.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 RTMKit plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for RTMKit in the list. Note whether it is active or inactive.
    Affected if RTMKit plugin is installed and active
  2. Identify RTMKit version
    Click on the plugin name/link to view details, or inspect the plugin file header in wp-content/plugins/rtmkit/rtmkit.php to find the Version line.
    Affected if Version is unknown, unpatched, or falls within an affected range if such a range becomes known
  3. Verify the AJAX endpoint is accessible
    Check if the file ajax/get_submission_content.php or similar exists in the plugin directory, and confirm WordPress ajax functionality is enabled (default).
    Affected if The get_submission_content AJAX endpoint exists and responds to requests
  4. Identify users with Contributor role or higher
    In WordPress admin, go to Users and review the role column. Note any accounts assigned Contributor, Author, Editor, or Administrator roles.
    Affected if There are users with Contributor-level access or higher who could potentially make requests to the endpoint
  5. Check if current_user_can() is present in the endpoint
    Examine the get_submission_content AJAX handler code in the plugin files. Search for a current_user_can() capability check before returning submission data.
    Affected if No capability check exists, or the check is missing/insufficient before returning form submission data

If RTMKit is active, the vulnerable get_submission_content endpoint is exposed, and users with Contributor-level access exist without proper capability checks in the endpoint code, the environment is affected.

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

Add a WordPress capability check (e.g., current_user_can()) to the get_submission_content AJAX endpoint to verify the user has appropriate permissions before returning form submission data, and validate that the requested entry belongs to a form the user is authorized to access.

Recommended fix High confidence

Version 2.0.8 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the RTMKit plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the updated plugin from the WordPress plugin repository and upload it manually

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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