dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-66127

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-16
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 g5theme Essential Real Estate essential-real-estate allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Essential Real Estate: from n/a through <= 5.3.2.

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 Essential Real Estate WordPress theme/plugin allows unauthenticated or lower-privileged users to access functionality that should be restricted to higher-privilege users due to missing or insufficient access control checks on certain endpoints or functions.

MitigationImplement proper role-based access control (RBAC) and authorization verification on all sensitive functions and endpoints, ensuring that user permissions are validated before executing privileged operations.

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. Confirm Essential Real Estate installation
    Check WordPress plugins directory for 'essential-real-estate' folder or view in WP Admin > Plugins. Alternatively, search for 'Essential Real Estate' in theme files or plugin files.
    Affected if Essential Real Estate theme or plugin is installed on the WordPress site
  2. Identify installed version
    Read the main plugin file (usually essential-real-estate.php) or style.css in theme folder to find the Version: header. In WP Admin, go to Plugins > Installed Plugins and look for the version number.
    Affected if Version cannot be determined or is at any version (no fixed version range provided)
  3. Review REST API endpoints
    Query the site's REST API routes by visiting /wp-json/ and look for endpoints under 'essential-real-estate' namespace. Check if sensitive endpoints (e.g., /wp-json/ere/v1/property/, /ere/v1/agent/, /ere/v1/submit-property/) accept requests without requiring authentication.
    Affected if REST API endpoints accessible without authentication or without capability checks
  4. Check AJAX actions
    Review plugin JavaScript files and PHP action handlers for wp_ajax_ and wp_ajax_nopriv_ hooks. Look for actions handling sensitive operations like property submission, user management, or data export.
    Affected if AJAX actions registered with wp_ajax_nopriv_ and perform privileged operations without capability verification
  5. Inspect capability checks in code
    Search plugin PHP files for current_user_can(), wp_get_current_user(), or get_role() calls around sensitive functions. Identify functions or endpoints that lack these checks before executing privileged operations.
    Affected if Sensitive functions execute without current_user_can() verification or equivalent authorization checks

The site is affected if Essential Real Estate is installed and sensitive REST API endpoints, AJAX actions, or functions lack proper capability/authorization verification allowing access by unauthenticated or low-privileged users.

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

Implement proper role-based access control (RBAC) and authorization verification on all sensitive functions and endpoints, ensuring that user permissions are validated before executing privileged operations.

Recommended fix Moderate confidence

Latest version of Essential Real Estate plugin (version > 5.3.2)

  1. 1. Verify the current installed version of the Essential Real Estate plugin in WordPress admin under Plugins > Installed Plugins
  2. 2. Check the g5theme official source (ThemeForest or g5theme.com) for the latest version of Essential Real Estate
  3. 3. Update the plugin to the latest available version that includes the security fix for the Missing Authorization vulnerability (CWE-862)
  4. 4. After updating, verify that the authorization controls are properly functioning for all user roles
  5. 5. Test that regular subscribers/users cannot access administrative functions that should be restricted
Caveat Review plugin changelog for any breaking changes between your current version and the new version before upgrading

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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