CVE-2018-7590
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 · uneditedCSRF exists in Hoosk 1.7.0 via /admin/users/new/add, resulting in account creation.
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 confidenceA CSRF vulnerability in Hoosk 1.7.0 allows attackers to craft malicious requests to /admin/users/new/add that trick authenticated administrators into creating unauthorized user accounts without their knowledge or consent.
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= 1.7.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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.
-
Identify Hoosk versionLocate the Hoosk installation and check the version number in the source code, configuration files, or admin panel. Common locations include a version.php file, composer.json, or the admin dashboard.Affected if The installed version is exactly 1.7.0
-
Verify admin endpoint existsConfirm that the /admin/users/new/add endpoint is accessible and functional in your Hoosk installation by attempting to access it via the admin interface or reviewing routing configuration.Affected if The endpoint exists and accepts POST requests for user creation
-
Check for anti-CSRF token on user creation formInspect the HTML source of the admin user creation form (typically at /admin/users/new or similar) and look for a hidden input field containing a CSRF token, or check if the form submits to an endpoint that validates such tokens.Affected if No CSRF token is present in the user creation form, or the token is not validated server-side on submission to /admin/users/new/add
-
Check session cookie SameSite attributeUse browser developer tools or a command-line HTTP client to examine the session cookie Set-Cookie header and verify if the SameSite attribute is set to a restrictive value (Strict or Lax).Affected if The session cookie lacks a SameSite attribute or is set to None without secure flag, making CSRF attacks possible
You are affected if you are running Hoosk version 1.7.0 and the user creation form at /admin/users/new/add lacks anti-CSRF token protection.
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 on all state-changing forms including user creation, validate the Origin/Referer headers server-side, and configure SameSite attributes on session cookies to prevent cross-site request forgery attacks.
- Consultation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7590 — 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-7590 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