-
Notifications
You must be signed in to change notification settings - Fork 249
Update dependency @intlify/core-base to v11.1.10 [SECURITY] #5531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
openverse-bot
wants to merge
1
commit into
main
Choose a base branch
from
gha-renovatenpm-intlify-core-base-vulnerability
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update dependency @intlify/core-base to v11.1.10 [SECURITY] #5531
openverse-bot
wants to merge
1
commit into
main
from
gha-renovatenpm-intlify-core-base-vulnerability
+35
−32
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Latest k6 run output1Footnotes
|
63284b7 to
ca5bd00
Compare
94b297a to
3020e83
Compare
da1adde to
4947ec9
Compare
3112246 to
e846ee9
Compare
492d975 to
36f1428
Compare
1a658b0 to
24d28d3
Compare
24d28d3 to
dc4ea05
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
💻 aspect: code
Concerns the software code in the repository
dependencies
Pull requests that update a dependency file
🧰 goal: internal improvement
Improvement that benefits maintainers, not users
🟩 priority: low
Low priority and doesn't need to be rushed
🧱 stack: frontend
Related to the Nuxt frontend
🟨 tech: javascript
Involves JavaScript
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
11.0.1->11.1.10GitHub Vulnerability Alerts
CVE-2025-53892
Summary
The escapeParameterHtml: true option in Vue I18n is designed to protect against HTML/script injection by escaping interpolated parameters. However, this setting fails to prevent execution of certain tag-based payloads, such as
<img src=x onerror=...>, if the interpolated value is inserted inside an HTML context using v-html.This may lead to a DOM-based XSS vulnerability, even when using escapeParameterHtml: true, if a translation string includes minor HTML and is rendered via v-html.
Details
When escapeParameterHtml: true is enabled, it correctly escapes common injection points.
However, it does not sanitize entire attribute contexts, which can be used as XSS vectors via:
<img src=x onerror=alert(1)>PoC
In your Vue I18n configuration:
Use this interpolated payload:
const payload = '<script>alert("xss")</script>';Render the translation using v-html (even not using v-html):
<p v-html="$t('vulnerable', { payload })"></p>Expected: escaped content should render as text, not execute.
Actual: script executes in some environments (or the payload is partially parsed as HTML).
Impact
This creates a DOM-based Cross-Site Scripting (XSS) vulnerability despite enabling a security option (escapeParameterHtml) .
Release Notes
intlify/vue-i18n (@intlify/core-base)
v11.1.10Compare Source
🔒 Security Fixes
Full Changelog: intlify/vue-i18n@v11.1.9...v11.1.10
v11.1.9Compare Source
Full Changelog: intlify/vue-i18n@v11.1.8...v11.1.9
v11.1.8Compare Source
What's Changed
⚡ Improvement Features
Full Changelog: intlify/vue-i18n@v11.1.7...v11.1.8
v11.1.7Compare Source
What's Changed
🐛 Bug Fixes
Full Changelog: intlify/vue-i18n@v11.1.6...v11.1.7
v11.1.6Compare Source
What's Changed
⚡ Improvement Features
useI18ncalling on local scope by @kazupon in https://github.com/intlify/vue-i18n/pull/2203Full Changelog: intlify/vue-i18n@v11.1.5...v11.1.6
v11.1.5Compare Source
What's Changed
🐛 Bug Fixes
Full Changelog: intlify/vue-i18n@v11.1.4...v11.1.5
v11.1.4Compare Source
What's Changed
🌟 Features
⚡ Improvement Features
Full Changelog: intlify/vue-i18n@v11.1.3...v11.1.4
v11.1.3Compare Source
What's Changed
🐛 Bug Fixes
⚡ Improvement Features
Full Changelog: intlify/vue-i18n@v11.1.2...v11.1.3
v11.1.2Compare Source
What's Changed
🔒 Security Fixes
handleFlatJson, about details see GHSA-p2ph-7g93-hw3mFull Changelog: intlify/vue-i18n@v11.1.1...v11.1.2
v11.1.1Compare Source
Full Changelog: intlify/vue-i18n@v11.1.0...v11.1.1
v11.1.0Compare Source
What's Changed
🌟 Features
ComponentCustomProperties['$i18n']type by @BobbieGoede in https://github.com/intlify/vue-i18n/pull/2094📝️ Documentations
Full Changelog: intlify/vue-i18n@v11.0.1...v11.1.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled because a matching PR was automerged previously.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.