dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-47486

MEDIUM · 5.3 CVSS v3.1 Published 2025-05-07
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
Missing Authorization vulnerability in CyberChimps Responsive Plus responsive-add-ons allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Responsive Plus: from n/a through <= 3.1.9.

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 · moderate confidence

Missing Authorization vulnerability in CyberChimps Responsive Plus WordPress plugin allows unauthenticated or lower-privileged users to access administrative or privileged functionality that should be protected by Access Control Lists (ACLs). This authorization bypass affects versions up to and including 3.1.9 of the responsive-add-ons component.

MitigationUpdate to the latest version of Responsive Plus once available. Until then, restrict access to the affected functionality at the server level (e.g., via firewall rules or disabling the plugin if not needed) and monitor for unauthorized access attempts.

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 Responsive Plus plugin is installed
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Responsive Add-Ons' or 'Responsive Plus' by CyberChimps in the list of active plugins.
    Affected if The plugin is present and active in the WordPress installation.
  2. Identify responsive-add-ons component version
    In WordPress admin, go to Plugins > Installed Plugins and locate the Responsive Add-Ons plugin entry. The version number is displayed beneath the plugin name. Alternatively, check the version in the plugin's main PHP file header (typically in /wp-content/plugins/responsive-add-ons/ or similar path).
    Affected if The displayed version is 3.1.9 or lower.
  3. Inspect admin AJAX endpoints for authorization gaps
    Review the plugin's PHP files, particularly ajax-handler files, to identify admin-action functions that lack capability checks or nonce verification. Look for hooks like wp_ajax_responsive_add_ons_* that may be accessible to unauthenticated users.
    Affected if Admin AJAX actions exist without current_user_capability() checks or without proper authorization verification.
  4. Test unauthenticated access to admin functionality
    Attempt to access known admin URLs or AJAX endpoints provided by the plugin while logged out (using a tool like curl or Burp). Compare the response to expected access-denied behavior.
    Affected if Unauthenticated requests return successful responses for admin-level actions that should require elevated privileges.

A WordPress site running Responsive Add-Ons version 3.1.9 or lower is affected if the plugin exposes administrative functionality that can be accessed without proper authorization checks.

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

Update to the latest version of Responsive Plus once available. Until then, restrict access to the affected functionality at the server level (e.g., via firewall rules or disabling the plugin if not needed) and monitor for unauthorized access attempts.

Recommended fix Moderate confidence

Latest version of CyberChimps Responsive Plus (newer than 3.1.9)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Responsive Plus' or 'CyberChimps Responsive Plus' plugin
  4. 4. Check the currently installed version number
  5. 5. If the installed version is <= 3.1.9, navigate to Plugins > Add New
  6. 6. Search for 'Responsive Plus' or 'CyberChimps Responsive Plus'
  7. 7. Update to the latest available version from the official WordPress repository
  8. 8. Verify the update was successful and test the site functionality
Caveat Review plugin changelog for any breaking changes or deprecated features before updating

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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