BINLOG REPLAY privilege is sufficient to manipulate history of any versioned table

create database db;

create table db.t (a int) with system versioning;

create user ubinlog;

grant BINLOG REPLAY on *.* to ubinlog;

--connect(con1,localhost,ubinlog,,)

# Format description event

BINLOG '

719BYw8BAAAA/AAAAAABAAAAAAQAMTAuMTEuMC1NYXJpYURCLWRlYnVnLWxvZwAAAAAAAAAAAAAA

AAAAAAAAAAAAAAAAAADvX0FjEzgNAAgAEgAEBAQEEgAA5AAEGggAAAAICAgCAAAACgoKAAAAAAAA

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

AAAAAAAAAAAEEwQADQgICAoKCgFOe+tK

'/*!*/;

# Write event, inserting a 3-field row into db.t table

BINLOG '

KmBBYxMBAAAALgAAAMQDAAAAABIAAAAAAAEAAmRiAAF0AAMDERECBgYH/lbeqQ==

KmBBYxcBAAAANAAAAPgDAAAAABIAAAAAAAEAA//4AQAAAGHPfWAAAABjsLDgAAAAwopO7w==

'/*!*/;

--disconnect con1

--connection default

select a, row_start, row_end from db.t for system_time all;

# Cleanup

drop database db;

drop user ubinlog;

connection default;

select a, row_start, row_end from db.t for system_time all;

a	row_start	row_end

1	2022-01-01 00:00:00.000000	2023-01-01 00:00:00.000000