Skip to content

External Libraries: Update jQuery Form to version 4.4.0. - #16038

Closed
desrosj wants to merge 1 commit into
WordPress:trunkfrom
desrosj:update/jquery-form-4.4.0
Closed

desrosj wants to merge 1 commit into
WordPress:trunkfrom
desrosj:update/jquery-form-4.4.0

Conversation

@desrosj

@desrosj desrosj commented Nov 16, 2026 •

Copy link
Copy Markdown
Member

Updates jQuery Form from 4.3.0 to 4.4.0 and bumps the registered script version in script-loader.php so that cached copies are invalidated.

This release fixes four cross-site scripting vulnerabilities, adds support for jQuery 4, and fixes several long-standing bugs. See the 4.4.0 release notes.

Core registers the jquery-form handle but does not use it, so the impact is limited to plugins and themes that enqueue it. A few behavior changes could affect them:

  • JSON responses are parsed with JSON.parse only. JSON that only eval accepted (single quotes, unquoted keys) now fails with a parse error.
  • target only inserts string responses. Responses already parsed as JSON or XML are no longer inserted.
  • Iframe responses that fail to parse report parsererror instead of success with no data.

Trac ticket: Core-66711

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: Reviewing the release notes for risk, applying the version updates, and drafting this description. Changes were reviewed by me.


This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

🤖 Generated with Claude Code

@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 desrosj.

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 or WordPress.org 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.

@peterwilsoncc peterwilsoncc left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank @desrosj, this looks good to me and builds as expected.

wporg-sync pushed a commit that referenced this pull request Nov 17, 2026
Updates the jQuery Form library from version `4.3.0` to `4.4.0`. This release includes hardening fixes, adds support for jQuery 4 and fixes several long-standing bugs.

Core registers the `jquery-form` script handle but does not use it, so this update only affects plugins and themes that enqueue it. The following behavior changes may affect them:

* JSON responses are now parsed only with `JSON.parse()`. Responses that were previously accepted through `eval()`, such as those with single quotes or unquoted keys, now fail with a parse error.
* The `target` option now only inserts string responses. Responses that have already been parsed as JSON or XML are no longer inserted.
* Iframe responses that fail to parse now report `parsererror` instead of `success` with no data.

A full list of changes can be found on GitHub: jquery-form/form@v4.3.0...v4.4.0.

Developed in: #16038

Props desrosj.
Fixes #66711.


git-svn-id: https://develop.svn.wordpress.org/trunk@65541 602fd350-edb4-49c9-b593-d223f7449a82
@github-actions

Copy link
Copy Markdown

A commit was made that fixes the Trac ticket referenced in the description of this pull request.

SVN changeset: 65541
GitHub commit: dfd3b0e

This PR will be closed, but please confirm the accuracy of this and reopen if there is more work to be done.

@github-actions github-actions Bot closed this Nov 17, 2026
wporg-sync pushed a commit to WordPress/WordPress that referenced this pull request Nov 17, 2026
Updates the jQuery Form library from version `4.3.0` to `4.4.0`. This release includes hardening fixes, adds support for jQuery 4 and fixes several long-standing bugs.

Core registers the `jquery-form` script handle but does not use it, so this update only affects plugins and themes that enqueue it. The following behavior changes may affect them:

* JSON responses are now parsed only with `JSON.parse()`. Responses that were previously accepted through `eval()`, such as those with single quotes or unquoted keys, now fail with a parse error.
* The `target` option now only inserts string responses. Responses that have already been parsed as JSON or XML are no longer inserted.
* Iframe responses that fail to parse now report `parsererror` instead of `success` with no data.

A full list of changes can be found on GitHub: jquery-form/form@v4.3.0...v4.4.0.

Developed in: WordPress/wordpress-develop#16038

Props desrosj.
Fixes #66711.

Built from https://develop.svn.wordpress.org/trunk@65541


git-svn-id: http://core.svn.wordpress.org/trunk@64614 1a063a9b-81f0-0310-95a4-ce76da25c4cd
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.

2 participants