WisskiDrupal extension · Wiss Ki
CVE-2026-13239
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 · uneditedMissing Authorization vulnerability in Drupal WissKI allows Forceful Browsing. This issue affects WissKI versions: from 0.0.0 to 4.2.0.
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 confidenceDrupal WissKI versions 0.0.0 through 4.2.0 contain a missing authorization vulnerability that allows forceful browsing, enabling unauthenticated or unauthorized users to access sensitive endpoints or data that should require proper authentication and permission checks.
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
WisskiDrupal extension
< 4.2CVSS 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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.
-
Confirm Drupal WissKI module is installedRun 'drush pm-list --status=enabled' or check the modules directory for the wisski module folder in sites/all/modules or web/modulesAffected if WissKI module is present in the Drupal installation
-
Identify installed WissKI versionRun 'drush pm-info wisski' or check the info file (wisski.info.yml or wisski.info) for the version numberAffected if Version is 4.2.0 or lower (within 0.0.0 through 4.2.0 range)
-
Test for unauthenticated endpoint accessUse a browser or curl to attempt access to common WissKI endpoints (such as wisski/path/* routes, data endpoints, or API paths) without logging inAffected if Sensitive data or endpoints return HTTP 200 without authentication
-
Verify authorization configurationCheck Drupal permissions at /admin/people/permissions for WissKI-specific permissions and review role permissions assigned to anonymous usersAffected if Anonymous or unauthenticated roles have access to sensitive WissKI operations or data views
If WissKI version 4.2.0 or lower is installed AND sensitive endpoints are accessible without authentication, the environment is affected by this missing authorization vulnerability.
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 data4.2
Apply the vendor patch or update to a version beyond 4.2.0 that includes proper authorization checks for all sensitive endpoints; if no patch is available, manually audit and enforce access controls on all WissKI routes.
Fix this in Wisski
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-2026-13239 — 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-13239 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