CVE-2025-64378
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 CridioStudio ListingPro listingpro allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects ListingPro: from n/a through < 2.9.10.
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 confidenceThis is a missing authorization vulnerability in the ListingPro WordPress theme that allows authenticated or unauthenticated users to access functionality they should not have access to due to incorrectly configured access control security levels. The vulnerability exists in versions prior to 2.9.10.
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
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Locate the ListingPro theme installationCheck your WordPress installation at /wp-content/themes/listingpro/ or view the theme in WordPress admin under Appearance > ThemesAffected if The listingpro theme folder exists in your WordPress themes directory
-
Identify the installed versionOpen the theme's style.css file in the listingpro theme folder and look for the 'Version:' header in the file comments, or check via WordPress admin theme details panelAffected if The version number found is lower than 2.9.10 (e.g., 2.9.9, 2.8.x, etc.)
-
Confirm the theme is activeIn WordPress admin, go to Appearance > Themes and verify ListingPro is the currently active themeAffected if ListingPro is active and the version is prior to 2.9.10
-
Check for unauthorized access capabilityReview the theme's functionality files (functions.php, any plugin files included with the theme) for AJAX endpoints, admin pages, or callback functions that lack capability checks or nonce verificationAffected if Sensitive functions are accessible without proper authorization checks and theme version is prior to 2.9.10
Your environment is affected if the ListingPro theme is installed and active with a version number lower than 2.9.10.
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.
dbcve · scopedUpdate ListingPro to version 2.9.10 or later which contains proper authorization controls. If immediate update is not possible, review and restrict access to sensitive functionality until the patch can be applied.
ListingPro version 2.9.10
- 1. Backup your WordPress site and database before performing any updates.
- 2. Navigate to Dashboard > Updates in your WordPress admin panel, or check for updates within the ListingPro theme/plugin.
- 3. Update ListingPro to version 2.9.10 or the latest available version.
- 4. Verify the update was successful by checking the theme/plugin version number.
- 5. Test that the authorization controls are functioning correctly for affected features.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64378 — 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-64378 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