column reference "page_title" is ambiguous

[OatmealDome]

DynamicPageList3 version: 3.5.1
MediaWiki version: 1.39.8
PHP version: 7.4.33

List of steps to reproduce (step by step, including full links if applicable):

Attempt to use the following transclusion (used on https://wiki.dolphin-emu.org/index.php?title=Template:Navigation/Super_Mario):

{{#dpl:linksfrom=Template:Navigation/Super Mario/doc|notuses=Template:Navigation/Super Mario|notcategory=Navigation|notcategory=Platforms|notcategory=Series|reset=all}} 

What happens?:

The following database error occurs:

Error 42702: ERROR: column reference "page_title" is ambiguous
LINE 1: ...l2.cl_to IS NULL AND ecl3.cl_to IS NULL GROUP BY page_title...
^

Function: MediaWiki\Extension\DynamicPageList3\Query::buildAndSelect - Template:Navigation-Super_Mario
Query: SELECT DISTINCT pagesrc.page_title AS "sel_title",pagesrc.page_namespace AS "sel_ns","page".page_namespace AS "page_namespace","page".page_id AS "page_id","page".page_title AS "page_title" FROM "pagelinks" "plf","page" "pagesrc","page" LEFT OUTER JOIN "categorylinks" "ecl1" ON (("page".page_id = ecl1.cl_from AND ecl1.cl_to ='Navigation')) LEFT OUTER JOIN "categorylinks" "ecl2" ON (("page".page_id = ecl2.cl_from AND ecl2.cl_to ='Platforms')) LEFT OUTER JOIN "categorylinks" "ecl3" ON (("page".page_id = ecl3.cl_from AND ecl3.cl_to ='Series')) WHERE "page".page_is_redirect = 0 AND ("page".page_namespace = plf.pl_namespace) AND ("page".page_title = plf.pl_title) AND (pagesrc.page_id = plf.pl_from) AND ((plf.pl_from = 28269)) AND ("page".page_id NOT IN (SELECT "templatelinks".tl_from FROM "templatelinks" INNER JOIN "linktarget" ON "linktarget".lt_id = "templatelinks".tl_target_id WHERE (("linktarget".lt_namespace=10 AND "linktarget".lt_title = 'Navigation/Super_Mario')))) AND ecl1.cl_to IS NULL AND ecl2.cl_to IS NULL AND ecl3.cl_to IS NULL GROUP BY page_title LIMIT 500 OFFSET 0

What should have happened instead?:

An error does not occur.

Browser information, screenshots and other applicable information:

Updating to 3.5.2 results in a similar, but separate error that breaks all of our pages. I'll file a bug report for that later.