DirectorypressWordPress extension · Designinvento
CVE-2024-38755
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 Special Elements used in an SQL Command ('SQL Injection') vulnerability in Designinvento DirectoryPress allows SQL Injection.This issue affects DirectoryPress: from n/a through 3.6.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 confidenceSQL injection vulnerability in Designinvento DirectoryPress allows attackers to inject malicious SQL commands via unsanitized user input. The vulnerability affects all versions up to 3.6.10 and could enable unauthorized database access, data exfiltration, or modification.
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.10CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Check DirectoryPress versionLocate the version file in your DirectoryPress installation (typically version.php, index.php, or in the admin dashboard under plugin/theme information). Compare the version number to the affected range.Affected if Installed version is 3.6.10 or lower.
-
Identify user input points that interact with the databaseReview your DirectoryPress installation for forms, search fields, filters, URL parameters, or any feature that accepts user data and uses it in database queries. Common areas include search functionality, category filters, listing submissions, and user profile fields.Affected if User input fields exist that accept and process data without apparent sanitization.
-
Inspect database query code for unsanitized inputExamine PHP files in your DirectoryPress installation, particularly in directories handling search, listings, categories, and user submissions. Look for SQL query construction that directly incorporates user input (from $_GET, $_POST, $_REQUEST) without using prepared statements or escaping functions.Affected if Code directly concatenates user-supplied variables into SQL queries without parameterization.
-
Verify input validation is absent or insufficientCheck the same PHP files for input validation routines (such as type checking, length limits, or allowlist validation) applied before user input is used in database operations.Affected if No validation or weak validation is found on user input before it reaches SQL queries.
You are affected if DirectoryPress version is 3.6.10 or lower and your installation contains database queries that incorporate user input without proper sanitization or parameterized queries.
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 DirectoryPress to the latest patched version. If no patch is available, implement parameterized queries or prepared statements for all database interactions and apply input validation on all user-supplied data before using it in SQL queries.
Fix this in Directorypress
Scoped from the published advisory
- 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-2024-38755 — 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-38755 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