HustleWordPress extension · Incsub
CVE-2018-18576
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 Hustle (aka wordpress-popup) plugin through 6.0.5 for WordPress allows Directory Traversal to obtain a directory listing via the views/admin/dashboard/ URI.
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 confidenceThe Hustle (wordpress-popup) plugin through version 6.0.5 for WordPress contains a directory traversal vulnerability in the views/admin/dashboard/ URI handler. This allows unauthenticated attackers to traverse the filesystem and obtain directory listings, potentially exposing sensitive file paths and configurations.
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
HustleWordPress extension
<= 6.0.5CVSS 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 Hustle plugin is installedIn WordPress admin, navigate to Plugins > Installed Plugins and locate 'Hustle' in the list. Alternatively, check the file system at wp-content/plugins/ for the hustler plugin directory.Affected if The Hustle plugin directory exists in the WordPress plugins folder.
-
Identify installed Hustle versionIn WordPress admin, click on the Hustle plugin entry to view version details, or open the main plugin file (e.g., wordpress-popup.php) and locate the 'Version' header in the plugin metadata.Affected if The installed version is 6.0.5 or lower.
-
Verify vulnerable URI handler existsCheck if the file wp-content/plugins/wordpress-popup/views/admin/dashboard/ exists and is accessible via HTTP requests. Attempt to access a known path like /wp-admin/admin-ajax.php?action=hustle_views_admin_dashboard or similar endpoint that routes to views/admin/dashboard/.Affected if The views/admin/dashboard/ handler is present and responds to web requests.
-
Check for directory traversal vulnerabilitySend a crafted HTTP request to the vulnerable endpoint with directory traversal sequences such as ../../ or ..%2f to test if the application permits filesystem traversal. Inspect the response for directory listings or exposed file paths.Affected if The application returns directory listings or reveals file paths when traversal sequences are included in the request.
A user is affected if the Hustle plugin version is 6.0.5 or lower and the views/admin/dashboard/ handler is accessible and allows directory traversal via crafted requests.
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 Hustle plugin to a version newer than 6.0.5 which contains the patch for this vulnerability. Additionally, implement web application firewall rules to detect and block directory traversal patterns in incoming requests.
Fix this in Hustle
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-2018-18576 — 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-2018-18576 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