CVE-2025-60103
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-plugin allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects ListingPro: from n/a through <= 2.9.8.
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 confidenceThe ListingPro WordPress plugin (version <= 2.9.8) contains a Missing Authorization vulnerability where incorrectly configured access control allows users to perform actions or access resources beyond their intended privilege level. This broken access control flaw likely stems from missing capability checks or improper validation of user permissions on certain plugin functions or pages.
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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm ListingPro plugin is installedNavigate to WordPress admin > Plugins and look for 'ListingPro' in the list of installed plugins, or check the /wp-content/plugins/listingpro directory exists on the serverAffected if ListingPro plugin is present in the WordPress installation
-
Check installed version numberIn WordPress admin > Plugins, find ListingPro and view the version number under the plugin name, or inspect the main plugin file header for the 'Version' fieldAffected if Version is 2.9.8 or lower
-
Verify plugin is activeIn WordPress admin > Plugins, confirm the ListingPro plugin shows as 'Active'Affected if Plugin is currently activated
-
Identify users with administrative accessGo to WordPress admin > Users and review which accounts have the Administrator role, then check if any lower-privileged roles (Editor, Author, Contributor, Subscriber) have been granted custom capabilities that should be restrictedAffected if Non-administrator users exist with elevated capabilities or access to admin functions they should not have
-
Audit plugin settings pages for unauthorized accessAs a non-administrator user (or by viewing page source), attempt to access ListingPro admin pages (typically under Listings > Settings, Listings > Listings, or similar plugin-specific admin menus) using a limited-role accountAffected if A user without Administrator role can view or modify plugin settings or listing data
The environment is affected if ListingPro plugin version 2.9.8 or lower is installed and active, and any non-administrator user can access plugin admin functions or data they should not be able to view or modify.
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 dataImplement proper authorization checks (capability/permission verification) on all sensitive plugin functions and admin pages. Update to the latest patched version of ListingPro if available, or disable the affected plugin until a fix is applied.
- 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-60103 — 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-60103 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