Clipperz data import is ignoring "hidden" fields and mapping the wrong password value #24365

Steps To Reproduce

1. Make a Clipperz account with secrets having multiple "hidden" properties, and export the file as html/json.
2. Go to "Tools > Import" then select "Clipperz (html)"
3. Click on "Import" and choose your file

Expected Result

I would expect that

1. All "locked" (for lack of a better word - there is no term in the UI) fields would be imported as Hidden fields
2. Password value would be correctly identified from among locked values

Actual Result

I am getting lots of bogus values for the password field (values from other "locked" fields not called "password"). And other locked fields do not import as Hidden custom fields. With a large import size, it's a mess, actually.

Screenshots or Videos

No response

Additional Context

I am guessing that the import tool expects only one "hidden" field, and uses the last listed hidden field value as the password value. The others are ignored. It should at least import all the locked fields and hidden fields, and hopefully prefer fields called "password" as the password value.

Operating System

Linux

Operating System Version

No response

Web Browser

Firefox

Browser Version

No response

Build Version

I don't see a build version listed

Issue Tracking Info

• I understand that work is tracked outside of GitHub. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.