CVE-2026-3489
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 DirectoryPress – Business Directory And Classified Ad Listing plugin for WordPress is vulnerable to SQL Injection via the 'packages' parameter in versions up to, and including, 3.6.26 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
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 DirectoryPress WordPress plugin versions up to 3.6.26 are vulnerable to SQL Injection via the 'packages' parameter. Insufficient input escaping combined with unparameterized SQL queries allows unauthenticated attackers to inject arbitrary SQL commands and extract sensitive database information.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 DirectoryPress plugin is installedAccess WordPress admin dashboard and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a directorypress folderAffected if DirectoryPress plugin is not found in the WordPress installation
-
Identify installed DirectoryPress versionIn WordPress admin, find DirectoryPress in the plugins list and note the version number displayed, or check the main plugin file (e.g., directorypress.php) for the 'Version' header commentAffected if The installed version is 3.6.26 or any lower version number
-
Verify the packages functionality is activeCheck if the DirectoryPress listings directory is publicly accessible and the packages/listing options feature is enabled in plugin settings. The vulnerability is exploitable when the packages parameter handling code is reachable.Affected if The packages feature or listing package selection is enabled and publicly accessible to unauthenticated users
-
Inspect the packages parameter handling in codeExamine the PHP file(s) handling the 'packages' parameter (typically in includes/ajax-handlers.php or similar) for unparameterized SQL queries using the packages variable directly in WHERE clausesAffected if The code shows direct insertion of the packages parameter into SQL queries without prepare() statements or escaping functions
The environment is affected if DirectoryPress plugin version 3.6.26 or lower is installed and the packages feature is accessible, as the vulnerable unparameterized SQL query using the packages parameter can be exploited by unauthenticated attackers.
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 DirectoryPress plugin to a version newer than 3.6.26 which contains proper input sanitization and prepared statements for the 'packages' parameter.
- Consultation2.0 h
- Implementation1.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3489 — 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-2026-3489 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