Passer la navigation

[Résolu] Vulnerability in wp-views. Using vulnerable version of Select2 v4.0.3

This support ticket is created Il y a 4 months, 3 weeks. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Fuseau horaire du supporter : Asia/Kolkata (GMT+05:30)

Ce sujet contient 4 réponses, a 1 voix.

Dernière mise à jour par Minesh Il y a 4 months, 2 weeks.

Assisté par: Minesh.

Auteur
Publications
#2843533

Hi,

My client sent a penetration test report indicating the wp-views plugin is using a vulnerable version of a JS library(Select2 v4.0.3). May I know what should I do?

#2843569

Minesh
Supporter

Les langues: Anglais (English )

Fuseau horaire: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

I've escalated the issue in front of our Devs and I will get in touch with you as soon as I have any update on it.

#2843573

Minesh
Supporter

Les langues: Anglais (English )

Fuseau horaire: Asia/Kolkata (GMT+05:30)

I got the news that we will try to update the select2 library packate to latest one with the next release that is scheduled to be by this month end or early Feb-2026. There is no perfect date but we will try our best in order to fix this issue as earliest.

#2844015

Hi. Is there a way to expedite? Since it's a vulnerability issue

#2844080

Minesh
Supporter

Les langues: Anglais (English )

Fuseau horaire: Asia/Kolkata (GMT+05:30)

I got the reply from our Dev:

Most penetration scanners flag Select2 ≤ 4.0.3 because of CVE-2017-1000189 / related advisories, which describe:
- XSS risk via unescaped HTML in results or placeholders
- ONLY exploitable if untrusted user input is rendered as HTML
- ONLY relevant when Select2 is used in public-facing forms

Key point:
Select2 itself is not remotely exploitable by default.
It becomes exploitable only when developers pass unsanitized user input into Select2 with escapeMarkup disabled or custom templates.

However - we will give priority to this issue as we can.

In wp-views, Select2 is used primarily for:
- Admin UI
- Editor dropdowns
- Backend configuration panels

Important facts:
- It is not exposed to anonymous users
- Inputs are controlled and sanitized
- No escapeMarkup: false usage with user input