Skip to content

fix(deps): update bump-dependencies - #23

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate.bump-dependencies
Open

fix(deps): update bump-dependencies#23
renovate[bot] wants to merge 1 commit into
mainfrom
renovate.bump-dependencies

Conversation

@renovate

@renovaterenovateBot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

PackageTypeUpdateChangeAgeConfidence
axllent/mailpit (source)digestb868afad5ecbb0
libops/basedigestaa0c61057b396f
libops/mariadbdigest7e0eb9052bc6b8
libops/wpfinaldigestfb32fa4cf9c391
roots/wordpress (source)requirepatch7.0.27.0.4ageconfidence
traefik (source)patchv3.7.9v3.7.10ageconfidence
wpackagist-plugin/akismet (source)requirepatch5.75.7.1ageconfidence

Release Notes

roots/wordpress (roots/wordpress)

v7.0.4: Version 7.0.4

Compare Source

Sourced from WordPress.org Documentation.

Summary

Security updates

This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:

  • An authenticated Author+ remote code execution issue via malicious file upload on sites that use Imagick and Ghostscript reported by the team at pwn.ai

As a courtesy, these fixes are also available in older affected branches of WordPress. As a reminder, only the most recent version of WordPress is actively supported.

  • WordPress 6.9 is affected by this vulnerability. Version 6.9.7 has been released containing a fix.
  • WordPress 6.8 is affected by this vulnerability. Version 6.8.8 has been released containing a fix.
  • WordPress 6.7 is affected by this vulnerability. Version 6.7.7 has been released containing a fix.
  • WordPress 6.6 is affected by this vulnerability. Version 6.6.7 has been released containing a fix.
  • WordPress 6.5 is affected by this vulnerability. Version 6.5.10 has been released containing a fix.
  • WordPress 6.4 is affected by this vulnerability. Version 6.4.10 has been released containing a fix.
  • WordPress 6.3 is affected by this vulnerability. Version 6.3.10 has been released containing a fix.
  • WordPress 6.2 is affected by this vulnerability. Version 6.2.11 has been released containing a fix.
  • WordPress 6.1 is affected by this vulnerability. Version 6.1.12 has been released containing a fix.
  • WordPress 6.0 is affected by this vulnerability. Version 6.0.14 has been released containing a fix.
  • WordPress 5.9 is affected by this vulnerability. Version 5.9.16 has been released containing a fix.
  • WordPress 5.8 is affected by this vulnerability. Version 5.8.15 has been released containing a fix.
  • WordPress 5.7 is affected by this vulnerability. Version 5.7.17 has been released containing a fix.
  • WordPress 5.6 is affected by this vulnerability. Version 5.6.19 has been released containing a fix.
  • WordPress 5.5 is affected by this vulnerability. Version 5.5.20 has been released containing a fix.
  • WordPress 5.4 is affected by this vulnerability. Version 5.4.21 has been released containing a fix.
  • WordPress 5.3 is affected by this vulnerability. Version 5.3.23 has been released containing a fix.
  • WordPress 5.2 is affected by this vulnerability. Version 5.2.26 has been released containing a fix.
  • WordPress 5.1 is affected by this vulnerability. Version 5.1.24 has been released containing a fix.
  • WordPress 5.0 is affected by this vulnerability. Version 5.0.27 has been released containing a fix.
  • WordPress 4.9 is affected by this vulnerability. Version 4.9.31 has been released containing a fix.
  • WordPress 4.8 is affected by this vulnerability. Version 4.8.30 has been released containing a fix.
  • WordPress 4.7 is affected by this vulnerability. Version 4.7.35 has been released containing a fix.
  • WordPress 4.6 and earlier no longer receive security updates.

v7.0.3: Version 7.0.3

Compare Source

Sourced from WordPress.org Documentation.

Summary

Security updates

This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:

  • A Contributor+ stored cross-site scripting (XSS) issue in the Post Date block reported by Alex Concha of the WordPress Security Team
  • A Contributor+ stored cross-site scripting (XSS) issue in the Post Content block reported by n05ec
  • An information disclosure issue in the Latest Comments block exposing comments on password-protected posts reported by Ehtisham Siddiqui of the WordPress Security Team
  • A bypass of the email address confirmation flow reported by 0ways
  • An Author+ CSS injection issue via a bypass of the safe CSS attribute filter reported by Anthropic
  • A Contributor+ stored cross-site scripting (XSS) issue in posts via the emoji settings element reported by Asaf Mozes (amosec)
  • A privilege escalation issue on multisite networks with user registration enabled, allowing a user to create a new site reported by Aikido Security
  • A server-side request forgery (SSRF) issue in URL validation allowing requests to link-local ranges reported by Andrew Mohawk and multiple independent reporters
  • A pre-auth reflected cross-site scripting (XSS) issue on the login screen with potential to lead to PHP code execution reported by the team at pwn.ai
  • A disclosure of notes in comment feeds reported by Elio Gubser
  • An enumeration of post slugs reported by HDWSec
  • A Contributor+ stored cross-site scripting (XSS) issue in Quick Edit on sites with a large number of users reported by Naveen S and Ajmal Moochingal

As a courtesy, these fixes are also available in older affected branches of WordPress. As a reminder, only the most recent version of WordPress is actively supported.

  • WordPress 6.9 is affected by 11 of the 12 vulnerabilities. Version 6.9.6 has been released containing fixes.
  • WordPress 6.8 is affected by 8 of the 12 vulnerabilities. Version 6.8.7 has been released containing fixes.
  • WordPress 6.7 is affected by 8 of the 12 vulnerabilities. Version 6.7.6 has been released containing fixes.
  • WordPress 6.6 is affected by 8 of the 12 vulnerabilities. Version 6.6.6 has been released containing fixes.
  • WordPress 6.5 is affected by 8 of the 12 vulnerabilities. Version 6.5.9 has been released containing fixes.
  • WordPress 6.4 is affected by 8 of the 12 vulnerabilities. Version 6.4.9 has been released containing fixes.
  • WordPress 6.3 is affected by 8 of the 12 vulnerabilities. Version 6.3.9 has been released containing fixes.
  • WordPress 6.2 is affected by 8 of the 12 vulnerabilities. Version 6.2.10 has been released containing fixes.
  • WordPress 6.1 is affected by 8 of the 12 vulnerabilities. Version 6.1.11 has been released containing fixes.
  • WordPress 6.0 is affected by 8 of the 12 vulnerabilities. Version 6.0.13 has been released containing fixes.
  • WordPress 5.9 is affected by 8 of the 12 vulnerabilities. Version 5.9.14 has been released containing fixes.
  • WordPress 5.8 is affected by 8 of the 12 vulnerabilities. Version 5.8.14 has been released containing fixes.
  • WordPress 5.7 is affected by 7 of the 12 vulnerabilities. Version 5.7.16 has been released containing fixes.
  • WordPress 5.6 is affected by 7 of the 12 vulnerabilities. Version 5.6.18 has been released containing fixes.
  • WordPress 5.5 is affected by 7 of the 12 vulnerabilities. Version 5.5.19 has been released containing fixes.
  • WordPress 5.4 is affected by 7 of the 12 vulnerabilities. Version 5.4.20 has been released containing fixes.
  • WordPress 5.3 is affected by 7 of the 12 vulnerabilities. Version 5.3.22 has been released containing fixes.
  • WordPress 5.2 is affected by 7 of the 12 vulnerabilities. Version 5.2.25 has been released containing fixes.
  • WordPress 5.1 is affected by 7 of the 12 vulnerabilities. Version 5.1.23 has been released containing fixes.
  • WordPress 5.0 is affected by 7 of the 12 vulnerabilities. Version 5.0.26 has been released containing fixes.
  • WordPress 4.9 is affected by 7 of the 12 vulnerabilities. Version 4.9.30 has been released containing fixes.
  • WordPress 4.8 is affected by 7 of the 12 vulnerabilities. Version 4.8.29 has been released containing fixes.
  • WordPress 4.7 is affected by 7 of the 12 vulnerabilities. Version 4.7.34 has been released containing fixes.
  • WordPress 4.6 and earlier no longer receive security updates.
containous/traefik (traefik)

v3.7.10

Compare Source

All Commits

Bug fixes:

Documentation:

  • [k8s/ingress-nginx] Clarify auth-url/rewrite-target interaction on ingress-nginx provider (#​13607@​gndz07)

v3.7.10

Compare Source

All Commits

Bug fixes:

Documentation:

  • [k8s/ingress-nginx] Clarify auth-url/rewrite-target interaction on ingress-nginx provider (#​13607@​gndz07)

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Only on Wednesday (* * * * 3)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovateBotforce-pushed the renovate.bump-dependencies branch 8 times, most recently from 825fd7f to 553b5abCompareAugust 7, 2026 23:35
@renovaterenovateBot changed the title chore(deps): update bump-dependenciesfix(deps): update bump-dependenciesAug 7, 2026
@renovate
renovateBotforce-pushed the renovate.bump-dependencies branch 10 times, most recently from efdab8b to 752cbcdCompareAugust 12, 2026 16:46
@renovate
renovateBotforce-pushed the renovate.bump-dependencies branch from 752cbcd to 0649f6cCompareAugust 18, 2026 01:15
@renovate
renovateBotforce-pushed the renovate.bump-dependencies branch from 0649f6c to 957bfe0CompareAugust 18, 2026 17:01
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants