CVE-2025-32252
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 · uneditedMissing Authorization vulnerability in Black and White WP Genealogy – Your Family History Website wpgenealogy allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Genealogy – Your Family History Website: from n/a through <= 0.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 confidenceMissing authorization vulnerability in the WP Genealogy plugin allows attackers to access resources or functionality they shouldn't have permission to access due to incorrectly configured access control security levels. This is a broken access control issue where the plugin fails to properly verify user permissions before granting access to sensitive functionality.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP Genealogy plugin is installedCheck for the plugin directory at wp-content/plugins/ and look for a folder containing 'genealogy' in the name. Also check the WordPress admin plugin list.Affected if The plugin files are present in the WordPress installation
-
Identify the installed versionOpen the main plugin file (typically wp-content/plugins/[genealogy-folder]/[genealogy-file].php) and locate the version comment or Version header in the plugin file header.Affected if The installed version is older than the patched version (compare against the latest version available from the plugin developer)
-
Test admin page access with low-privilege userCreate or use a subscriber-level user account and attempt to access the WP Genealogy admin pages directly via URL (e.g., admin.php?page=wp-genealogy or similar).Affected if The low-privilege user can access admin pages without proper authorization
-
Verify capability checks on plugin actionsReview the plugin source code for functions that handle admin actions (add, edit, delete operations) and check if they include current_user_can() or similar permission checks before executing sensitive operations.Affected if Admin functions lack proper capability checks or authorization verification
-
Check for exposed AJAX endpointsExamine the plugin for AJAX handlers (wp_ajax_ and wp_ajax_nopriv_ hooks) and test if actions that should require authentication are accessible to unauthenticated users.Affected if Sensitive AJAX endpoints are accessible without authentication or proper authorization
A user is affected if the WP Genealogy plugin is installed and admin functions or sensitive features are accessible to users lacking proper WordPress capabilities or authorization.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to the latest version of the plugin when available. Until then, restrict access to the plugin's admin functions to trusted users only and monitor for unauthorized access attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32252 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-32252 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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