CVE-2025-32249
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Designinvento DirectoryPress directorypress allows Cross Site Request Forgery.This issue affects DirectoryPress: from n/a through <= 3.6.22.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in DirectoryPress plugin versions through 3.6.22 allows attackers to induce authenticated users to perform unwanted actions (such as modifying directory entries or settings) by tricking them into visiting malicious pages. The plugin lacks proper anti-CSRF token validation on sensitive state-changing requests.
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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Locate DirectoryPress plugin filesCheck your WordPress installation under wp-content/plugins/ for a directory named 'directorypress' or similar. Alternatively, log into WordPress admin and navigate to Plugins > Installed Plugins to verify DirectoryPress is listed.Affected if DirectoryPress plugin is not found in the plugins directory or not listed in WordPress admin.
-
Identify the installed versionOpen the main DirectoryPress plugin file (usually directorypress.php) and locate the version comment at the top of the file (e.g., 'Version: x.x.x'). Alternatively, view the plugin details in WordPress admin Plugins page.Affected if The version number cannot be determined or is at or below 3.6.22.
-
Verify version is within affected rangeCompare your installed version against 'through 3.6.22'. If your version is 3.6.22 or any earlier version, it falls within the affected range.Affected if Installed version is 3.6.22 or earlier.
-
Inspect state-changing actions for nonce validationExamine the DirectoryPress plugin code files that handle form submissions or URL actions for modifying directory entries or settings (commonly found in includes/, admin/, or shortcodes/ directories). Look for calls to wp_nonce_field(), wp_verify_nonce(), or check_admin_referer() on POST or GET requests that change data.Affected if State-changing operations (such as adding/editing listings, updating settings, or deleting entries) lack nonce validation code and are accessible without a valid anti-CSRF token.
You are affected if DirectoryPress plugin is installed with version 3.6.22 or earlier AND sensitive actions lack anti-CSRF token (nonce) validation in the plugin code.
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 anti-CSRF tokens (nonce validation) on all state-changing operations (POST/GET requests), validate Origin/Referer headers server-side, and consider adding SameSite cookie attributes. Upgrade to the latest DirectoryPress version if a patch is available.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32249 — 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-32249 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