Winbox timeout with wireguard

I have configured two Wireguard VPNs, one for my phone and one for my laptop which are both working fine (surfing from home network, reaching server/services) except that I get a connection timeout error when trying to connect to Winbox from my laptop (can’t try with the phone).
Everything I found about this issue was that people where missing accept rules but i have those so could you please tell me if there’s something wrong with them?

My complete firewall:

add action=accept chain=input comment="defconf: accept established,related,untracked" connection-state=established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=invalid
add action=accept chain=input comment="defconf: accept ICMP" protocol=icmp
add action=accept chain=input comment="defconf: accept to local loopback (for CAPsMAN)" dst-address=127.0.0.1
add action=accept chain=input comment="VPN-WG-MyPhone access" dst-port=10131 protocol=udp
add action=accept chain=input comment="VPN-WG-MyPhone access" dst-address=192.168.131.1 in-interface=VPN-WG-MyPhone
add action=accept chain=input comment="VPN-WG-MyLaptop access" dst-port=10132 protocol=udp
add action=accept chain=input comment="VPN-WG-MyLaptop access" dst-address=192.168.132.1 in-interface=VPN-WG-MyLaptop
add action=drop chain=input comment="defconf: drop all not coming from LAN" in-interface=!Bridge-LAN
add action=accept chain=forward comment="defconf: accept in ipsec policy" ipsec-policy=in,ipsec
add action=accept chain=forward comment="defconf: accept out ipsec policy" ipsec-policy=out,ipsec
add action=fasttrack-connection chain=forward comment="defconf: fasttrack" connection-state=established,related hw-offload=yes
add action=accept chain=forward comment="defconf: accept established,related, untracked" connection-state=established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" connection-state=invalid
add action=drop chain=forward comment="defconf: drop all from WAN not DSTNATed" connection-nat-state=!dstnat connection-state=new in-interface=Bridge-WAN

we need to guess the rest of your configuration?

What filter rule do you assume to allow access from Winbox?
By far the easiest way to grant access is to add the wireguard interface to your LAN interface list.

Why do you think that the firewall is where the problem is…