Fill in card incorrect expiry format

[JABirchall]

Steps To Reproduce

1. Go to payment page
2. Click on bitwarden > fillin card
3. Scroll down to observe expiry date is incorrect format

Bitwarden is filling in card expiry date incorrectly, some time in the past 3 months, bitwarden has gone from the correct format the wrong format.

Currently is is doing Year / Month
Almost every website is expecting Month / Year

Expected Result

Card expiry to be filled correctly

Month / Year

Actual Result

Card expiry is filled in the wrong order.

Year / Month

Screenshots or Videos

I double checked in bitwarden and the card details are in the correct format in bitwarden.

Additional Context

This was on the checkpage https://ukvapekings.com/checkout/

Operating System

Windows

Operating System Version

No response

Web Browser

Firefox

Browser Version

No response

Build Version

2024.11.*
Further regression 2025.1.*

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.

[bitwarden-bot]

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-15866

[Krychaz]

Hi there,

Thank you for your report!

I was able to reproduce this issue, and I have flagged this to our engineering team.

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.

Thanks once again!

[VarunAgw]

+1

[bwbug]

FWIW, I have also noticed this behavior happening more frequently in the recent past.

[rhys100]

• • drives me nuts everyday

heres what bitwarden has for expiry of a credit card

this is what it enters on the form

[raestanton]

+1

definitely happening more since the upgraded design of the chrome extension!

[Damecek]

Time to time happens that the date won't be filled at all as it expect different format than bitwarden is using, mm/yyyy, vs mm/yy.

[JABirchall]

Ive noticed this too.

In the past week bitwarden has gone from

YY/MM to switching between YYYY/MM or MM/YYYY

It is randomly switching between year first or second, but is now constantly trying to put in all 4 digits of the year. So if the site expects MM/YY you get 20/27 or 02/20 for example.

This issue is regressing in version 2025.1.*

[bwbug]

The pattern is that when autofilling a MM/YY field, the 2nd and 3rd digits of the year are autofilled as the month value, while the 4th digit of the year and the first digit of the month are autofilled as the year value.

11/2027 → 02/71
05/4123 → 12/30
12/2034 → 03/41

It is quite reproducible, so someone who has the time and inclination to dig through the code should be able to find this bug.