Use of Client-Side Authentication in Płatnik
Affects Płatnik up to metric 242 in version 10.02.002, where a party with access to an application instance connected to the backend server can bypass the login check. The checked facts give no vendor rating or fix.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in metric 242
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Płatnik, a software application, is affected by this vulnerability because it performs authentication on the client side rather than the server. An attacker who can use any Płatnik application instance connected to the backend server could bypass the login check and sign in as any user.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Płatnik performs client-side authentication. An attacker with access to any application instance connected to the backend server can bypass the login verification process and authenticate as an arbitrary user. This issue was fixed in metric 242 in version 10.02.002.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Zakład Ubezpieczeń Społecznych Płatnik
fixed in metric 242
References 2
Questions about CVE-2026-110972
What does this mean?
The flaw lets an attacker bypass the login verification process and authenticate as an arbitrary user. The attacker needs access to an application instance of Płatnik that is connected to the backend server.Source: cert.pl
Am I affected, and how do I check?
The checked facts list all Płatnik versions up to metric 242 in version 10.02.002. To check a installation, compare its version and metric against that range in the product's version information.Source: cert.pl
What should I do about it?
The checked facts do not name a fixed version, so no upgrade target can be given from them. Consult the vendor's advisory from Zakład Ubezpieczeń Społecznych for the fixed release.Source: cert.pl
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data