LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36365: Smartstore (aka SmartStoreNET) before 4.1.0 allows CommonController.ClearCache, ClearDatabaseCache, Restart...

Smartstore (aka SmartStoreNET) before 4.1.0 allows CommonController.ClearCache, ClearDatabaseCache, RestartApplication, and ScheduleTaskController.Edit open redirect.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

Smartstore versions before 4.1.0 contain open redirect behavior in specific controller actions. In business terms, a trusted Smartstore link could send a user to an unintended external site. The provided sources do not show direct data theft, server compromise, CVSS scoring, or active exploitation.

Executive priority

Treat this as a targeted hygiene issue unless Smartstore is internet-facing or heavily used by administrators. The absence of scoring and exploitation evidence limits urgency, but affected versions should still be retired through normal patch governance.

Technical view

The CVE describes open redirects in Smartstore, also called SmartStoreNET, before 4.1.0. Named actions are CommonController.ClearCache, ClearDatabaseCache, RestartApplication, and ScheduleTaskController.Edit. The source bundle provides no CVSS vector, CWE, authentication context, exploitability detail, or vendor remediation text beyond the version boundary.

Likely exposure

Exposure is limited to organizations running Smartstore or SmartStoreNET before 4.1.0. Risk depends on whether the affected routes are reachable in deployed environments and whether access controls restrict them. The provided evidence does not define affected CPEs or authentication requirements.

Exploitation context

CISA KEV is false, and the supplied sources do not report active exploitation. Open redirects are commonly useful for phishing or trust-abuse chains, but this analysis should not assume weaponization for this CVE without additional evidence.

Researcher notes

Evidence is sparse. The CVE text identifies affected actions and a pre-4.1.0 version boundary, but lacks CVSS, CWE, CPEs, authentication details, and exploit-status confirmation. Validate against the GitHub issue and local routing behavior before assigning operational severity.

Mitigation direction

  • Inventory Smartstore or SmartStoreNET deployments and record exact versions.
  • Prioritize upgrade planning for instances older than 4.1.0.
  • Review the referenced GitHub issue for vendor-specific remediation context.
  • Restrict access to administrative routes where operationally possible.
  • Monitor vendor advisories for any corrected guidance or backports.

Validation and detection

  • Confirm whether each deployment runs Smartstore or SmartStoreNET before 4.1.0.
  • Map whether the named controller actions are reachable in production.
  • Review access controls protecting administrative and scheduled-task functionality.
  • Check web logs for unusual redirects involving the named actions.
  • Document any compensating controls if immediate upgrade is delayed.
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-36365 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
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

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.