dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-27310

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-17
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
Missing Authorization vulnerability in Radius of Thought Page and Post Lister page-and-post-lister allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Page and Post Lister: from n/a through <= 1.2.1.

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 the Radius of Thought Page and Post Lister WordPress plugin allows authenticated users to access functionality or data beyond their intended privilege level due to incorrectly configured access control security levels.

MitigationImplement proper role-based capability checks and authorization controls on all admin pages and API endpoints within the plugin; verify that the access control security levels are correctly configured according to WordPress user roles and capabilities.

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
None
Integrity
None
Availability
High

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

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. Identify if the Radius of Thought Page and Post Lister plugin is installed
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and search for 'Radius of Thought Page and Post Lister' or 'radius of thought'. Alternatively, check the /wp-content/plugins/ directory for a folder named similarly to the plugin.
    Affected if The plugin appears in the installed plugins list.
  2. Determine the installed plugin version
    In the WordPress admin, go to Plugins > Installed Plugins, find the plugin, and view the version number displayed below the plugin name. Alternatively, check the main plugin PHP file for a 'Version' header in the plugin comment block.
    Affected if A version number is displayed and matches or falls within an unpatched range.
  3. Verify WordPress user roles with access to plugin functionality
    Navigate to the plugin admin page (usually under Pages or a dedicated menu item named 'Page and Post Lister' or similar). Log in with different user roles (subscriber, contributor, author, editor) to determine which roles can access the plugin listing functionality.
    Affected if Lower-privileged roles such as subscribers, contributors, or authors can access and view the plugin's page or post listing functionality without proper authorization checks.
  4. Check for role-based access control on plugin endpoints
    Use a browser or HTTP tool to access plugin admin pages while logged in as a low-privilege user. Inspect whether the plugin returns post/page data or allows actions that should require higher privileges (like administrator or editor).
    Affected if The plugin returns data or allows actions that should be restricted to administrators or higher-privileged users.
  5. Inspect plugin capabilities configuration
    Examine the main plugin PHP file for 'capability' or 'manage_options' definitions. Check if capability checks are properly applied to admin menu items, page renders, and any AJAX or API endpoints the plugin exposes.
    Affected if The plugin lacks proper capability checks or uses overly permissive capability definitions (such as 'read' for admin-only functions).

A user is affected if the Radius of Thought Page and Post Lister plugin is installed and low-privileged authenticated users can access functionality or data that should be restricted to higher-privileged roles.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper role-based capability checks and authorization controls on all admin pages and API endpoints within the plugin; verify that the access control security levels are correctly configured according to WordPress user roles and capabilities.

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-2025-27310 — 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-27310 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