dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-3550

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 RockPress plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 1.0.17. This is due to missing capability checks on multiple AJAX actions (rockpress_import, rockpress_import_status, rockpress_last_import, rockpress_reset_import, and rockpress_check_services) combined with the plugin's nonce being exposed to all authenticated users via an unconditionally enqueued admin script. The plugin enqueues the 'rockpress-admin' script on all admin pages (including profile.php) without any page or capability restrictions, and the nonce for the 'rockpress-nonce' action is passed to this script via wp_localize_script. Since the AJAX handlers only verify this nonce and do not check current_user_can(), any authenticated user, including Subscribers, can extract the nonce from any admin page's HTML source and use it to trigger imports, reset import data (deleting options), check service connectivity, and read import status information. This makes it possible for authenticated attackers, with Subscriber-level access and above, to trigger resource-intensive import operations, reset import tracking data, and perform system connection checks that should be restricted to administrators.

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

The RockPress WordPress plugin (versions up to 1.0.17) lacks authorization checks on five AJAX actions (rockpress_import, rockpress_import_status, rockpress_last_import, rockpress_reset_import, and rockpress_check_services). These handlers only validate a nonce but do not call current_user_can(), and the nonce is exposed to all authenticated users via an unconditionally enqueued admin script. This allows any Subscriber-level user to trigger imports, delete options, and check services.

MitigationAdd current_user_can('manage_options') capability checks to all affected AJAX handlers and restrict the 'rockpress-admin' script enqueue to admin pages that actually require it.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Verify RockPress plugin is installed
    Go to WordPress admin > Plugins and confirm 'RockPress' appears in the list, or check the plugins directory for /wp-content/plugins/rockpress/
    Affected if RockPress plugin is not installed or not active - not affected
  2. Check installed version
    In Plugins list, note the version number listed under RockPress, or inspect the main plugin file header for 'Version:' value
    Affected if Version is 1.0.17 or lower (the vulnerability affects versions up to and including 1.0.17)
  3. Confirm AJAX endpoints exist
    Inspect the plugin source files for add_action("wp_ajax_rockpress_import") or similar hooks for the five actions: rockpress_import, rockpress_import_status, rockpress_last_import, rockpress_reset_import, rockpress_check_services
    Affected if Any of these AJAX handlers exist without current_user_can() capability checks - likely affected
  4. Check for subscriber-level users
    In WordPress admin > Users, review the user list to see if any accounts have the Subscriber role (or Author, Editor) rather than only Administrator
    Affected if There are users with Subscriber, Author, or Editor roles - these users can trigger the vulnerable AJAX actions
  5. Test AJAX accessibility (optional)
    As a Subscriber-level user, attempt a GET/POST to /wp-admin/admin-ajax.php with action=rockpress_import and verify if the request is processed rather than rejected
    Affected if The AJAX action processes requests from low-privileged users without checking capabilities - confirms the vulnerability is exploitable

You are affected if the RockPress plugin is active at version 1.0.17 or lower AND your site has any user with Subscriber, Author, or Editor role (which is any authenticated non-admin user).

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 current_user_can('manage_options') capability checks to all affected AJAX handlers and restrict the 'rockpress-admin' script enqueue to admin pages that actually require it.

Recommended fix Moderate confidence

RockPress version 1.0.18 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the RockPress plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Verify the update was successful and the plugin is now at version 1.0.18 or later
  6. 6. Test that the AJAX functionality still works correctly for administrator users
  7. 7. Confirm that non-administrator users can no longer access the vulnerable AJAX actions

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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