LiveActive security incident?Get immediate response
CVE Record

CVE-2020-23136: Microweber v1.1.18 is affected by no session expiry after log-out.

Microweber v1.1.18 is affected by no session expiry after log-out.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Microweber v1.1.18 reportedly does not invalidate a user's session when they log out. If a session token is already exposed or shared, logout may not end access as expected. The public record is sparse, so treat this as a session-management risk until vendor guidance confirms scope and remediation.

Executive priority

Prioritize if Microweber v1.1.18 is used for administration, customer portals, or shared-device workflows. This is not KEV-listed in the provided data, but session persistence after logout weakens account control and should be resolved during normal vulnerability remediation.

Technical view

The CVE record describes no session expiry after logout in Microweber v1.1.18. This suggests logout may not revoke an existing authenticated session. The source bundle lacks CVSS, CWE, CPEs, vendor advisory, patch status, and detailed reproduction boundaries.

Likely exposure

Likely limited to organizations running Microweber v1.1.18. The affected-products metadata is incomplete, and no CPEs are provided. Exposure depends on whether deployed instances keep authenticated sessions valid after logout.

Exploitation context

The bundle does not show CISA KEV listing or cited active exploitation. The referenced gist is the only technical reference, and the CVE record provides minimal detail. Risk centers on session tokens that remain usable after logout, especially on shared devices or if tokens are otherwise obtained.

Researcher notes

Evidence is limited to a sparse CVE description and one gist reference. No CVSS vector, CWE, affected CPEs, or official patch reference is included. Avoid broad product claims beyond Microweber v1.1.18 unless confirmed by vendor documentation.

Mitigation direction

  • Check Microweber vendor guidance for fixed versions or session-management configuration.
  • Upgrade away from Microweber v1.1.18 if vendor guidance identifies a corrected release.
  • Review session timeout and logout invalidation settings in deployed Microweber instances.
  • Reduce session lifetime for administrative users where configurable.
  • Require reauthentication for sensitive administrative actions.

Validation and detection

  • Inventory public and internal Microweber deployments and identify version 1.1.18.
  • Confirm whether logout invalidates the server-side session in a test environment.
  • Review application logs for continued session use after logout events.
  • Check vendor release notes or advisory channels for remediation details.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-23136 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
2Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.