CVE-2025-6745
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 · uneditedThe WoodMart plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 8.2.5 via the woodmart_get_posts_by_query() function due to insufficient restrictions on which posts can be included. This makes it possible for unauthenticated attackers to extract data from password protected, private, or draft posts that they should not have access to.
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 · high confidenceThe WoodMart WordPress plugin up to version 8.2.5 contains an information disclosure vulnerability in the woodmart_get_posts_by_query() function. The function fails to properly validate user permissions and post visibility status before returning post data, allowing unauthenticated attackers to query and extract sensitive content from password-protected, private, and draft posts.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm WoodMart plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WoodMart' in the list. Note whether it is active or inactive.Affected if WoodMart plugin is active and the version is 8.2.5 or lower
-
Identify installed WoodMart versionIn WordPress admin, go to Plugins > Installed Plugins, find WoodMart, and view the version number displayed under the plugin name. Alternatively, check the version in the plugin's main PHP file header (typically in woodmart/woodmart.php).Affected if The installed version is 8.2.5 or any version prior to 8.2.5
-
Check for sensitive post typesIn WordPress admin, go to Posts > All Posts and review the list for any posts with status 'Draft', 'Private', or those protected by password. Note the quantity and sensitivity of such posts.Affected if There are draft, private, or password-protected posts on the site that could be queried
-
Test endpoint accessibilityIf the site has WoodMart <=8.2.5 active, test whether the woodmart_get_posts_by_query function is exposed by making a request to /wp-admin/admin-ajax.php with action=woodmart_get_posts_by_query (this may require examining the plugin's JavaScript or AJAX handlers to confirm the exact endpoint).Affected if The AJAX endpoint for woodmart_get_posts_by_query is accessible without authentication
A site is affected if WoodMart plugin version 8.2.5 or lower is active AND there are draft, private, or password-protected posts that could be queried through the exposed function.
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 the WoodMart plugin to the latest version beyond 8.2.5 which should contain proper authorization checks. If immediate update is not feasible, disable or restrict access to the woodmart_get_posts_by_query() function until the patch can be applied.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6745 — 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-6745 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