It sounds like there's a whole lot going wrong with your Scrum process.
It's important to realize that a product backlog is not prioritized. It is ordered. There is no reference to a prioritized or priority-ordered Product Backlog anywhere in the Scrum Guide. In the section of the Scrum Guide about a Product Owner, it's implied that individual Product Backlog Items have a priority. However, the required attributes of a Product Backlog Item are a description, order, estimate, and value.
The Product Owner is the person responsible for managing the Product Backlog. Two of the Product Backlog management activities are "ordering the items in the Product Backlog to best achieve goals and missions" and "optimizing the value of the work the Development Team performs". Simply ordering the work based on priority to someone is not likely to put the items in the order that can accomplish these two activities.
The act of refining (or grooming) the Product Backlog is a collaboration between the Product Owner and the Development Team. This is a time for the Product Owner to explain the intentions behind the Product Backlog Items to the Development Team and review and revise them. This is also a good opportunity for the Development Team to highlight technical dependencies between Product Backlog Items. The discussions during refinement activities should inform the Product Owner to be able to make better decisions when ordering the backlog.
Based on the description of the process, I also have other concerns.
There appear to be three product-related roles mentioned - Product Owner, Business Analyst, and Product Manager. It's important that there is one Product Owner for the Product Backlog. It's OK for this person to have a team backing them up. In a scaled environment with multiple teams working on a single Product Backlog, you may also want to embed someone on each team. But no matter what, there is one person with the role of Product Owner as described in Scrum.
The Scrum Master also appears heavily involved in doing work. The Scrum Master is a coach. You don't say what their role is in managing the Product Backlog, but that they are allowing the Product Backlog to be ordered without input from the development team, they are not establishing and teaching good refinement or grooming activities that is inclusive of the whole team, and they are not teaching the Product Owner about optimizing for value and achieving goals is problematic.
There are also potential pitfalls around having a lead position on a Scrum Team, but these can generally be overcome by keeping the whole team involved at the right point in time and can be valuable to long-term success of a team.