CVE Intelligence
Skip to main content
MEDIUMpublic exploit

CVE-2022-4611

CVE-2022-4611 — Click Studios Passwordstate hard-coded credentials

A vulnerability, which was classified as problematic, was found in Click Studios Passwordstate and Passwordstate Browser Extension Chrome. This affects an unknown part. The manipulation leads to hard-coded credentials. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. It is recommended to upgrade the affected component. The identifier VDB-216273 was assigned to this vulnerability.

Published Updated Sources: cvelistV5, VulDB

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

1%

chance of exploitation in 30 days

Affects

click studios

2 products listed

CVSS base

4.3

MEDIUM

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

click studios

Products (2)

passwordstatepasswordstate browser extension chrome

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
4.3CVSS 3.1MEDIUM——cvelistV5

Weakness & attack patterns

  • CWE-798

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1552.001Unsecured Credentials: Credentials in files
  • T1078.001Valid Accounts: Default Accounts

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Indexed by

poc in github

References

3 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.