PYSEC-2021-341

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2020-18701: 2.28% estimated exploitation activity in the next 30 days; percentile 83.13 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Incorrect Access Control in Lin-CMS-Flask v0.1.1 allows remote attackers to obtain sensitive information and/or gain privileges due to the application not invalidating a user's authentication token upon logout, which allows for replaying packets.

Published by the source

16 Aug 2021, 18:15 UTC

Last modified by the source

9 Oct 2025, 07:55 UTC

Source last checked

24 Oct 2026, 04:13 UTC

1. Revision 1 · created · 24 Oct 2026

   Published from osv record PYSEC-2021-341

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-18701

Advisory: PYSEC-2021-341
IDs: CVE-2020-18701
Record: https://patchnext.com/advisories/cve-2020-18701 (revision 1, source checked 24 Oct 2026, 04:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI lin-cms: affected every version

## Suggested inspection (read-only)
- `python -m pip show lin-cms`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on lin-cms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/PYSEC-2021-341 (OSV record PYSEC-2021-341 lists affected ranges: PyPI lin-cms >=0)

Commands are suggestions: review each one before running it.