Skip to content

fix(deps): security bumps for 12 Dependabot alerts#1993

Open
rtBot wants to merge 1 commit into
mainfrom
deps/security-fixes-2026-06-30
Open

fix(deps): security bumps for 12 Dependabot alerts#1993
rtBot wants to merge 1 commit into
mainfrom
deps/security-fixes-2026-06-30

Conversation

@rtBot

@rtBot rtBot commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

Summary

Lockfile-focused security bumps addressing open Dependabot alerts for the npm ecosystem. All fixes stay within the same major version as installed (no breaking major bumps, no source edits). The repo uses overrides to pin transitive security versions; vulnerable pins were advanced to patched same-major releases, and posthog-js was bumped (per Dependabot PR #1961) to drop its vulnerable transitive dependencies.

Fixes

Package Old -> New Alert # Severity GHSA
dompurify (override) 3.4.5 -> 3.4.11 217,218,219,221,222,223,226 medium/low GHSA-r47g-fvhr-h676, -hpcv-96wg-7vj8, -76mc-f452-cxcm, -rp9w-3fw7-7cwq, -gvmj-g25r-r7wr, -vxr8-fq34-vvx9, -cmwh-pvxp-8882
ws (override) 8.20.1 -> 8.21.0 210 HIGH GHSA-96hv-2xvq-fx4p
form-data 4.0.5 -> 4.0.6 214 HIGH GHSA-hmw2-7cc7-3qxx
protobufjs (via posthog-js drop) 7.5.8 -> removed 216 HIGH GHSA-wcpc-wj8m-hjx6
protobufjs (via posthog-js drop) 7.5.8 -> removed 215 medium GHSA-f38q-mgvj-vph7
@babel/core (devDep + override) 7.28.0/7.25.7 -> 7.29.6 227, 211 low GHSA-4x5r-pxfx-6jf8
launch-editor 2.13.1 -> 2.14.1 213 medium GHSA-v6wh-96g9-6wx3
@opentelemetry/core 2.x (via posthog-js) 2.2.0/2.6.0 -> removed 224 (partial) medium GHSA-8988-4f7v-96qf

Why

  • dompurify/protobufjs/ws are pinned through the existing overrides block; bumping the override values to patched same-major versions is the repo's established mechanism for transitive security control.
  • posthog-js ^1.282.0 -> ^1.386.8 (matching Dependabot PR chore(deps): bump protobufjs and posthog-js #1961) eliminates the vulnerable transitive protobufjs and the @opentelemetry/core 2.x copies entirely.
  • @babel/core added to overrides so the nested dev-only @WordPress copies (7.25.7) dedupe to 7.29.6.

How tested

Lockfile-only changes generated with npm install/update --package-lock-only --ignore-scripts. The lockfile parses as valid JSON. Build/tests NOT run locally — please verify in CI.

Residual risk / not applied

  • Alert 220 — dompurify (low): No patched version exists (first_patched_version = none). Not fixable.
  • Alert 161 — showdown 1.9.1 (medium): No patched version exists. Major rewrite would be required. Not fixable.
  • Alert 225 — markdown-it 12.3.2 (medium): Patch is 14.2.0 — a major bump (12 -> 14). Out of safe scope; flagged for manual review.
  • Alert 224 — @opentelemetry/core (medium): The actively-flagged vulnerable 2.x copies were removed via the posthog-js bump. A residual dev-only @opentelemetry/core@1.30.1 remains (transitive of @sentry/node and the OTel 1.x instrumentation tree, which require ^1.x). The advisory patch is 2.8.0 — a major bump of that 1.x tree. Out of safe scope; flagged for manual review.

Do not merge without CI verification.

- dompurify override 3.4.5 -> 3.4.11 (GHSA-cmwh-pvxp-8882, -vxr8-fq34-vvx9, -gvmj-g25r-r7wr, -rp9w-3fw7-7cwq, -76mc-f452-cxcm, -hpcv-96wg-7vj8, -r47g-fvhr-h676)
- ws override <8.21.0:8.21.0 (GHSA-96hv-2xvq-fx4p)
- form-data -> 4.0.6 (GHSA-hmw2-7cc7-3qxx)
- launch-editor -> 2.14.1 (GHSA-v6wh-96g9-6wx3)
- @babel/core devDep + override -> 7.29.6 (GHSA-4x5r-pxfx-6jf8)
- posthog-js ^1.282.0 -> ^1.386.8, removing vulnerable protobufjs (GHSA-wcpc-wj8m-hjx6, -f38q-mgvj-vph7) and @opentelemetry/core 2.x copies (GHSA-8988-4f7v-96qf)

Build NOT run locally; lockfile-only. Verify in CI.
Copilot AI review requested due to automatic review settings June 30, 2026 09:58

Copilot AI 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.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@github-actions

Copy link
Copy Markdown

🔍 WordPress Plugin Check Report

❌ Status: Failed

📊 Report

🎯 Total Issues ❌ Errors ⚠️ Warnings
18 2 16

❌ Errors (2)

📁 lib/class-godam-frappe-dispatch-installer.php (2 errors)
📍 Line 🔖 Check 💬 Message
302 PluginCheck.CodeAnalysis.WriteFile.PluginDirectoryWrite Plugin folders are deleted when upgraded. Do not save data to the plugin folder using unzip_file(). Detected usage of constant WP_PLUGIN_DIR. Use wp_upload_dir() to get the uploads directory path or save to the database instead.
347 PluginCheck.CodeAnalysis.WriteFile.PluginDirectoryWrite Plugin folders are deleted when upgraded. Do not save data to the plugin folder using copy_dir(). Detected usage of constant WP_PLUGIN_DIR. Use wp_upload_dir() to get the uploads directory path or save to the database instead.

⚠️ Warnings (16)

📁 composer.json (1 warning)
📍 Line 🔖 Check 💬 Message
0 missing_composer_json_file The "/vendor" directory using composer exists, but "composer.json" file is missing.
📁 readme.txt (2 warnings)
📍 Line 🔖 Check 💬 Message
0 mismatched_plugin_name Plugin name "GoDAM - Organize WordPress Media Library & File Manager with Unlimited Folders for Images, Videos & more" is different from the name declared in plugin header "GoDAM".
0 trademarked_term The plugin name includes a restricted term. Your chosen plugin name - "GoDAM - Organize WordPress Media Library & File Manager with Unlimited Folders for Images, Videos & more" - contains the restricted term "wordpress" which cannot be used at all in your plugin name.
📁 assets/build/blocks/godam-gallery-v2/render.php (2 warnings)
📍 Line 🔖 Check 💬 Message
15 WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedVariableFound Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$inner_block_video_ids".
23 WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedVariableFound Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$inner_block_video_ids".
📁 assets/build/css/main.css (1 warning)
📍 Line 🔖 Check 💬 Message
0 EnqueuedStylesScope This style is being loaded in all contexts.
📁 assets/src/libs/analytics.min.js (5 warnings)
📍 Line 🔖 Check 💬 Message
0 EnqueuedScriptsScope This script is being loaded in all frontend contexts.
0 NonBlockingScripts.NoStrategy This script on http://localhost:8880 (with handle analytics-library) is loaded in the footer. Consider a defer or async script loading strategy instead.
0 NonBlockingScripts.NoStrategy This script on http://localhost:8880/2026/06/30/hello-world/ (with handle analytics-library) is loaded in the footer. Consider a defer or async script loading strategy instead.
0 NonBlockingScripts.NoStrategy This script on http://localhost:8880/sample-page/ (with handle analytics-library) is loaded in the footer. Consider a defer or async script loading strategy instead.
0 NonBlockingScripts.NoStrategy This script on http://localhost:8880/demo-attachment-post/ (with handle analytics-library) is loaded in the footer. Consider a defer or async script loading strategy instead.
📁 assets/build/js/main.min.js (5 warnings)
📍 Line 🔖 Check 💬 Message
0 EnqueuedScriptsScope This script is being loaded in all frontend contexts.
0 NonBlockingScripts.NoStrategy This script on http://localhost:8880 (with handle rtgodam-script) is loaded in the footer. Consider a defer or async script loading strategy instead.
0 NonBlockingScripts.NoStrategy This script on http://localhost:8880/2026/06/30/hello-world/ (with handle rtgodam-script) is loaded in the footer. Consider a defer or async script loading strategy instead.
0 NonBlockingScripts.NoStrategy This script on http://localhost:8880/sample-page/ (with handle rtgodam-script) is loaded in the footer. Consider a defer or async script loading strategy instead.
0 NonBlockingScripts.NoStrategy This script on http://localhost:8880/demo-attachment-post/ (with handle rtgodam-script) is loaded in the footer. Consider a defer or async script loading strategy instead.

🤖 Generated by WordPress Plugin Check Action • Learn more about Plugin Check

@dhruvikpatel18

Copy link
Copy Markdown

@subodhr258 I've reviewed this PR and built it locally, build succeeded with the dependent version changes. Should we go ahead and merge this to main?

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.

3 participants