langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Open Redirect Vulnerability in webapp-signin (redirect_url not validated) #15177

New Issue
Closed
opened 2026-02-21 19:20:33 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:20:33 -05:00
Owner
Copy Link
Copy Source

Originally created by @CHENFANGC on GitHub (Jul 8, 2025).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

v1.5.1

Cloud or Self Hosted

Cloud

Steps to reproduce

An open redirect vulnerability exists in the /webapp-signin route due to lack of validation on the redirect_url query parameter. By passing a malicious external URL, users can be redirected to arbitrary third-party domains after visiting a crafted link.

Example:
https://cloud.dify.ai/webapp-signin?redirect_url=https://www.baidu.com&web_sso_token=false&message=11
This URL causes an automatic redirect to https://www.baidu.com, which is outside the Dify trust boundary.

Visit:
https://cloud.dify.ai/webapp-signin?redirect_url=https://www.baidu.com&web_sso_token=false&message=11

You will be redirected to https://www.baidu.com immediately without validation.

✔️ Expected Behavior

The redirect should be either:

Validated against an allowlist of trusted domains (e.g., cloud.dify.ai)

Or strictly restricted to relative paths (e.g., /dashboard), which are resolved internally on the same domain.

❌ Actual Behavior

External URLs are accepted and executed without validation, enabling phishing or malicious redirection attacks.

Originally created by @CHENFANGC on GitHub (Jul 8, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version v1.5.1 ### Cloud or Self Hosted Cloud ### Steps to reproduce An open redirect vulnerability exists in the /webapp-signin route due to lack of validation on the redirect_url query parameter. By passing a malicious external URL, users can be redirected to arbitrary third-party domains after visiting a crafted link. Example: `https://cloud.dify.ai/webapp-signin?redirect_url=https://www.baidu.com&web_sso_token=false&message=11` This URL causes an automatic redirect to https://www.baidu.com, which is outside the Dify trust boundary. Visit: https://cloud.dify.ai/webapp-signin?redirect_url=https://www.baidu.com&web_sso_token=false&message=11 You will be redirected to https://www.baidu.com immediately without validation. ### ✔️ Expected Behavior The redirect should be either: Validated against an allowlist of trusted domains (e.g., cloud.dify.ai) Or strictly restricted to relative paths (e.g., /dashboard), which are resolved internally on the same domain. ### ❌ Actual Behavior External URLs are accepted and executed without validation, enabling phishing or malicious redirection attacks.
yindo added the 🐞 bugvulnerablity labels 2026-02-21 19:20:33 -05:00
yindo closed this issue 2026-02-21 19:20:33 -05:00
yindo commented 2026-02-21 19:20:33 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jul 8, 2025):

Please see this https://github.com/langgenius/dify?tab=readme-ov-file#security-disclosure

@crazywoola commented on GitHub (Jul 8, 2025): Please see this https://github.com/langgenius/dify?tab=readme-ov-file#security-disclosure
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label vulnerablity 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#15177
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?