dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-63002

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-18
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 wpforchurch Sermon Manager sermon-manager-for-wordpress allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Sermon Manager: from n/a through <= 2.30.0.

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

This is a Missing Authorization vulnerability in the Sermon Manager plugin for WordPress. The issue allows unauthorized users to access sermon data or functionality that should be restricted due to incorrectly configured access control security levels. The vulnerability requires no privileges or user interaction to exploit, with a CVSS base score of 5.3 indicating a medium-severity access control bypass.

MitigationApply the vendor patch (likely version 2.30.1 or higher) which should add proper capability checks and permission verification to all sensitive sermon management functions. Until then, restrict access to affected plugin endpoints via server-side configuration or disable public access to the sermon manager URLs.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Verify Sermon Manager plugin is installed
    Check for the presence of the Sermon Manager plugin in the WordPress site's plugin directory or via WordPress admin plugin list
    Affected if The Sermon Manager plugin is found to be installed on the WordPress site
  2. Identify installed Sermon Manager version
    Locate the plugin header in the main plugin file (typically wp-content/plugins/sermon-manager-for-wordpress/sermon-manager.php) or check the readme.txt file for the Version field
    Affected if The installed version cannot be determined to be 2.30.1 or higher (the patched version) or if the version is unknown
  3. Confirm plugin is active
    Check the WordPress admin under Plugins > Installed Plugins to verify the Sermon Manager plugin is activated
    Affected if The plugin is installed and active, exposing its functionality to the site
  4. Test for unauthorized access to sermon endpoints
    Attempt to access typical Sermon Manager URLs or AJAX actions (such as /wp-json/sermon-manager/v1/sermons or admin-ajax.php?action=get_sermons) without authentication or any user session
    Affected if Sermon data or plugin functionality is returned without requiring WordPress user authentication or proper capability checks (such as manage_options or edit_sermons)
  5. Review user role permissions for sermon functions
    Inspect the plugin settings under Sermon Manager > Settings to see if access control options are incorrectly set to allow public or subscriber-level access to sensitive sermon management features
    Affected if Sensitive sermon creation, editing, or deletion functions are accessible to unauthenticated users or low-privilege roles like Subscriber or Contributor

The environment is affected if the Sermon Manager plugin for WordPress is installed and active, and sermon data or management functions can be accessed without proper authentication or appropriate WordPress capability verification.

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

Apply the vendor patch (likely version 2.30.1 or higher) which should add proper capability checks and permission verification to all sensitive sermon management functions. Until then, restrict access to affected plugin endpoints via server-side configuration or disable public access to the sermon manager URLs.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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