dbcve.org
MicroweberApplication

CVE-2020-23136

MEDIUM · 5.5 CVSS v3.1 Published 2020-11-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
Microweber v1.1.18 is affected by no session expiry after log-out.

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 confidence

Microweber v1.1.18 fails to invalidate user sessions upon logout. When a user clicks logout, the server-side session is not destroyed, allowing the session identifier to remain valid and potentially be reused by an attacker who obtains the session token.

MitigationImplement proper session destruction by calling session_destroy() and clearing session cookies when users log out, and consider adding server-side session expiration timers.

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
MicroweberApplication
Affected:= 1.1.18

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Microweber version
    Locate the version file (composer.json, src/Microweber/functions/common.php, or admin dashboard > System > Info). Look for version 1.1.18 specifically.
    Affected if The installed version is exactly 1.1.18
  2. Find the logout controller
    Locate the user logout file, typically in /userfiles/modules/users/login.php or similar auth controller. Search for a 'logout' function or endpoint.
    Affected if The file exists in the expected location for this version
  3. Verify session destruction in logout code
    Open the logout handler file and search for 'session_destroy' or 'session_unset'. Check if these functions are called when the logout action executes.
    Affected if session_destroy() is NOT called in the logout function (code does not contain this call)
  4. Check session configuration
    Examine the session configuration in config/database.php or application config files. Verify if session.use_strict_mode is enabled or if server-side session expiration is set.
    Affected if No server-side session expiration is configured and session can be reused indefinitely after logout

You are affected if running Microweber version 1.1.18 and the logout code does not invoke session_destroy() to invalidate the session server-side, allowing token reuse.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper session destruction by calling session_destroy() and clearing session cookies when users log out, and consider adding server-side session expiration timers.

Fix this in Microweber Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-23136 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-23136 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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