Skip to content

REST API: Prevent a fatal error when a non-string template is sent to the posts endpoint - #15906

Open
dhrupo wants to merge 1 commit into
WordPress:trunkfrom
dhrupo:66652-rest-posts-template-type
Open

dhrupo wants to merge 1 commit into
WordPress:trunkfrom
dhrupo:66652-rest-posts-template-type

Conversation

@dhrupo

@dhrupo dhrupo commented Nov 11, 2026

Copy link
Copy Markdown

Sending an array as the template argument to the posts endpoint causes a PHP fatal error, even for a logged-out request, because argument validation runs before the permission check:

curl -X POST -d "template[]=" "http://localhost/wp-json/wp/v2/posts"

WP_REST_Posts_Controller::check_template() is the validate_callback for template, so it replaces the default schema validation, and the array reaches isset( $allowed_templates[ $template ] ). This PR runs rest_validate_request_arg() first, so a non-string value gets the standard rest_invalid_param 400 error ("template is not of type string."). Valid requests behave as before. The pages endpoint uses the same method, so it is covered too.

Trac ticket: https://core.trac.wordpress.org/ticket/66652

Testing

New tests test_create_item_with_non_string_template and test_update_item_with_non_string_template (--group 66652):

  • trunk: TypeError: Cannot access offset of type array in isset or empty in both tests
  • this PR: OK (2 tests, 9 assertions)
  • --group restapi: Tests: 4026, Assertions: 18134, Warnings: 4, Skipped: 2 (the 4 warnings are the existing PHPUnit 10 deprecation notices)
  • multisite, WP_Test_REST_Posts_Controller: OK (290 tests, 2651 assertions)

Live, WordPress 7.2-beta5-65392-src, PHP 8.4, logged out, POST /wp-json/wp/v2/posts with template[]=:

  • trunk: HTTP 500 (critical error page)
  • this PR: HTTP 400 {"code":"rest_invalid_param","message":"Invalid parameter(s): template","data":{"status":400,"params":{"template":"template is not of type string."}, …}}
  • unchanged: template= still gets 401, and template=x.php still gets 400 (not one of the allowed templates).

Use of AI Tools

AI assistance: Claude Code (Claude Opus 5.5) drafted the patch, the tests and the live reproduction; I reviewed every change, reproduced the fatal on trunk, and ran and verified all results myself.

… the posts endpoint.

`WP_REST_Posts_Controller::check_template()` replaces the default schema validation for the `template` argument, so an array value reached `isset( $allowed_templates[ $template ] )` and caused a fatal error. Validate the value against the schema type first, so it returns the standard `rest_invalid_param` error.

Props leedxw, dhrupo.
Fixes #66652.
@github-actions

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

Core Committers: Use this line as a base for the props when committing in SVN:

Props dhrupo.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.


Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

  • @propsbot add <username> to give props to a GitHub user. Requires write access.
  • @propsbot remove <username> to leave a user out of the props. Requires write access.
  • @propsbot refresh to refresh this list. Adding the props-bot label works too.

@github-actions

Copy link
Copy Markdown

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant