dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-30916

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/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 enituretechnology Residential Address Detection residential-address-detection allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Residential Address Detection: from n/a through <= 2.5.4.

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 Residential Address Detection WordPress plugin allows unauthenticated or improperly authenticated users to access functions that should require proper access control checks. The vulnerability stems from incorrectly configured access control security levels on certain plugin functions, likely AJAX actions or REST API endpoints that lack proper capability checks or nonce validation.

MitigationImplement proper authorization checks (capability checks and nonce verification) on all sensitive plugin functions, particularly AJAX handlers and API endpoints. Ensure all actions require appropriate user permissions before execution.

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
Low

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

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 the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Residential Address Detection' or check the wp-content/plugins directory for a folder named 'residential-address-detection' or similar. Check the plugin version listed.
    Affected if The plugin is installed and the version is within the affected range or unknown/older than a patched version
  2. Identify AJAX action handlers
    Examine the plugin PHP files for add_action('wp_ajax_...) or add_action('wp_ajax_nopriv_...) calls. Look for functions that handle sensitive operations (address data, user info, etc.) and check if they include current_user_can() capability checks or nonce verification.
    Affected if AJAX handlers exist that use wp_ajax_nopriv_ (allowing unauthenticated access) without proper current_user_can() checks or nonce validation
  3. Examine REST API endpoint registration
    Search plugin files for register_rest_route() calls. Check if each route includes a 'permission_callback' that properly validates user capabilities (e.g., permission_callback => function() { return current_user_can('manage_options'); })
    Affected if REST API routes are registered without a permission_callback or with a weak/always-true callback that allows unauthenticated access to sensitive functions
  4. Test unauthenticated access to plugin functions
    If the plugin exposes AJAX actions or REST endpoints, attempt to access them without authentication (e.g., send a request to /wp-admin/admin-ajax.php with action=plugin_action_name or to /wp-json/wp/v2/plugin_endpoint) and observe if the action executes without an error or redirect
    Affected if Sensitive plugin functions execute successfully when called without valid authentication credentials or without proper capability verification

A user is affected if the Residential Address Detection plugin is installed and its AJAX actions or REST API endpoints can be accessed or executed without proper authorization checks (capability verification and nonce validation).

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 authorization checks (capability checks and nonce verification) on all sensitive plugin functions, particularly AJAX handlers and API endpoints. Ensure all actions require appropriate user permissions before execution.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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