starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-25 06:06:05 +03:00

[GH-ISSUE #2063] Firefox plugin for floccus synchronization was detected as an XXE attack by the WAF #1380

New issue

Closed

opened 2026-02-25 22:39:51 +03:00 by kerem · 2 comments

kerem commented

2026-02-25 22:39:51 +03:00

Owner

Originally created by @tin607 on GitHub (Sep 18, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2063

Which version of floccus are you using?

5.7.0

How many bookmarks do you have, roughly?

Are you using other means to sync bookmarks in parallel to floccus?

Yes, I also sync via Google account

Sync method

WebDAV

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

No response

Which version of Nextcloud Bookmarks are you using? (if relevant)

No response

Which version of Nextcloud? (if relevant)

No response

What kind of WebDAV server are you using? (if relevant)

No response

Describe the Bug

The use of the Firefox plugin for floccus synchronization was detected as an XXE attack by the （safeline）WAF and was intercepted.

Expected Behavior

Does flocculus involve dangerous operations? I hope it can be improved.

To Reproduce

Debug log provided

I have provided a debug log file

Originally created by @tin607 on GitHub (Sep 18, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2063 ### Which version of floccus are you using? 5.7.0 ### How many bookmarks do you have, roughly? 30 ### Are you using other means to sync bookmarks in parallel to floccus? Yes, I also sync via Google account ### Sync method WebDAV ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. _No response_ ### Which version of Nextcloud Bookmarks are you using? (if relevant) _No response_ ### Which version of Nextcloud? (if relevant) _No response_ ### What kind of WebDAV server are you using? (if relevant) _No response_ ### Describe the Bug The use of the Firefox plugin for floccus synchronization was detected as an XXE attack by the （safeline）WAF and was intercepted. <img width="2453" height="320" alt="Image" src="https://github.com/user-attachments/assets/d2617121-0778-4782-8acb-b388f1db950b" /> <img width="2000" height="1382" alt="Image" src="https://github.com/user-attachments/assets/3da4beb7-ee16-4bcb-ba4e-d8768f6f6d03" /> ### Expected Behavior Does flocculus involve dangerous operations? I hope it can be improved. ### To Reproduce no ### Debug log provided - [ ] I have provided a debug log file

kerem

2026-02-25 22:39:51 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 22:39:51 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 18, 2025):

Hello! 👋

Thank you for taking the time to open this issue with floccus. I know it's frustrating when software causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud which leaves me with less time for side projects like this one than I used to have. I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it. Until then, please be patient. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general is a place where people meet to make software better together. Nobody here is under any obligation to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can collaborate to make this software better. For everyone. Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and try to fix the odd bug yourself. Everyone will be thankful for extra helping hands! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already. You can find donation options at https://floccus.org/donate/. Thank you!

One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum, to twitter or somewhere else. But this is a technical issue tracker, so please make sure to focus on the tech and keep your opinions to yourself.

Thank you for reading through this primer. I look forward to working with you on this issue! Cheers! 💙

@github-actions[bot] commented on GitHub (Sep 18, 2025): Hello! :wave: Thank you for taking the time to open this issue with floccus. I know it's frustrating when software causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud which leaves me with less time for side projects like this one than I used to have. I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it. Until then, please be patient. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general is a place where people meet to make software better *together*. Nobody here is under any obligation to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can collaborate to make this software better. For everyone. Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and try to fix the odd bug yourself. Everyone will be thankful for extra helping hands! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already. You can find donation options at <https://floccus.org/donate/>. Thank you! One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum, to twitter or somewhere else. But this is a technical issue tracker, so please make sure to focus on the tech and keep your opinions to yourself. Thank you for reading through this primer. I look forward to working with you on this issue! Cheers! :blue_heart:

kerem commented

2026-02-25 22:39:51 +03:00

Author

Owner

@marcelklehr commented on GitHub (Sep 18, 2025):

Hello @tin607
Thank you for taking the time to give feedback. Floccus does not do any XXE attack, it may be that the firewall just detects any XML payload as an XXE attack. You should check the payload of the request for external XML entities, there should be none.
Additionally, your screenshot includes your base64 encoded credentials. This is a public page. Please change your credentials immediately.

@marcelklehr commented on GitHub (Sep 18, 2025): Hello @tin607 Thank you for taking the time to give feedback. Floccus does not do any XXE attack, it may be that the firewall just detects any XML payload as an XXE attack. You should check the payload of the request for external XML entities, there should be none. Additionally, your screenshot includes your base64 encoded credentials. This is a public page. Please change your credentials immediately.

kerem referenced this issue

2026-02-25 23:31:06 +03:00

[PR #1380] [CLOSED] chore(deps-dev): bump vue-loader from 15.10.1 to 17.1.0 #1878

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/floccus#1380

No description provided.

Rows
Columns