DirectorypressWordPress extension · Designinvento
CVE-2024-32567
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Designinvento DirectoryPress allows Reflected XSS.This issue affects DirectoryPress: from n/a through 3.6.7.
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 confidenceReflected XSS vulnerability in Designinvento DirectoryPress plugin allows attackers to inject malicious scripts via improper neutralization of user input during web page generation. The vulnerability affects all versions up to 3.6.7.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
DirectorypressWordPress extension
< 3.6.8CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 DirectoryPress plugin installationCheck your WordPress plugins directory (typically wp-content/plugins/directorypress or similar naming) for the DirectoryPress plugin folderAffected if The DirectoryPress plugin folder exists on the server
-
Identify the installed DirectoryPress versionOpen the main plugin file (usually directorypress.php) or the plugin header comment and look for the Version: fieldAffected if The reported version number is less than 3.6.8 (e.g., 3.6.7, 3.6.6, etc.)
-
Verify the plugin is activeCheck the WordPress admin plugins page or database wp_options table for active_plugins entry referencing DirectoryPressAffected if DirectoryPress is currently activated on the site
-
Confirm the vulnerability scope appliesDetermine if the plugin handles user-supplied input via URL parameters (GET requests) that get reflected in the page output without sanitizationAffected if The plugin processes and displays user input from URL parameters on site pages
Your environment is affected if DirectoryPress plugin is installed with a version lower than 3.6.8 and is currently active on a WordPress site that processes user input through URL parameters.
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 · scoped3.6.8
Implement proper input validation, output encoding, and context-aware escaping on all user-supplied input parameters throughout the DirectoryPress plugin to prevent script injection.
DirectoryPress 3.6.8
- Backup your website database and files before making any changes
- Log in to your WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find DirectoryPress in the plugin list
- Click 'Update now' if an update is available, or manually upload DirectoryPress version 3.6.8
- Verify the installed version is 3.6.8 after updating
- Clear any caching plugins and test that the XSS vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Directorypress
Scoped from the published advisory
- 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-2024-32567 — 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-2024-32567 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