Team Member Team With SliderWordPress extension · Wpmart
CVE-2023-23647
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAuth. (author+) Stored Cross-Site Scripting (XSS) vulnerability in Sk. Abul Hasan Team Member – Team with Slider plugin <= 4.4 versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAuthenticated (author+) stored XSS vulnerability in the Sk. Abul Hasan Team Member WordPress plugin allows malicious JavaScript to be injected via plugin input fields and persistently stored, executing when other users view the affected content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Team Member Team With SliderWordPress extension
<= 4.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if the vulnerable plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for folders named 'team-member', 'sk-abul-hasan-team-member', 'wpmart-team-member', or similar team member related plugins. Alternatively, log into the WordPress admin and navigate to Plugins > Installed Plugins to list all active plugins.Affected if The plugin 'Sk. Abul Hasan Team Member' or 'Wpmart Team Member Team With Slider' appears in the installed plugins list
-
Check the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate the team member plugin. The version number is displayed under the plugin name. Alternatively, open the main plugin PHP file (e.g., team-member.php) and check the 'Version' header in the plugin comment block.Affected if The displayed version number is 4.4 or lower
-
Verify if the plugin team member functionality is in useNavigate to the WordPress admin panel and look for a 'Team Member' or 'Team With Slider' menu item (typically in the left sidebar). Check if any team members have been created and saved in the system.Affected if Team member entries exist in the plugin's content storage (database entries or published pages containing team member displays)
-
Confirm user access levels that can modify team member contentCheck WordPress user roles in Users > All Users. Determine if any users with 'Author' or higher role have access to the team member plugin creation/editing functionality. This typically requires Contributor, Author, Editor, or Administrator roles.Affected if There are users with Author or higher roles who have access to create or edit team member entries through this plugin
If the plugin is installed, the version is 4.4 or lower, team member entries exist, and author-level users can access the plugin functionality, the environment is affected by this stored XSS vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate the plugin to the latest version if available; otherwise, implement proper input sanitization and output encoding on all user-supplied data fields within the plugin.
Latest version available in WordPress plugin repository (version 4.5 or higher)
- 1. Update the Team Member – Team with Slider plugin to the latest available version from the WordPress plugin repository
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Team Member Team With Slider
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23647 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-23647 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data