Meet My TeamWordPress extension · Fullworksplugins
CVE-2022-37339
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 · uneditedAuthenticated (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Fullworks Meet My Team plugin <= 2.0.5 at WordPress.
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 · high confidenceAuthenticated contributor+ users can inject malicious JavaScript via the Meet My Team plugin's input fields, which is stored in the database and executes when other users view the team page. This is a stored XSS vulnerability stemming from insufficient input sanitization and output encoding in the plugin.
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
Meet My TeamWordPress extension
<= 2.0.5CVSS 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.
-
Verify Meet My Team plugin is installedNavigate to WordPress admin > Plugins and look for 'Meet My Team' by Fullworksplugins, or check the /wp-content/plugins/ directory for a meet-my-team folderAffected if The plugin is installed and active in WordPress
-
Check the installed version numberIn WordPress admin > Plugins > Installed Plugins, find Meet My Team and note the version number displayed, or read the version from the plugin header in its main PHP fileAffected if Version is 2.0.5 or lower
-
Identify users with contributor+ accessGo to WordPress admin > Users and note which users have contributor, author, editor, or administrator roles that can access the plugin's team member management interfaceAffected if Any user with contributor role or higher exists and can access the plugin admin area
-
Inspect plugin input fields for stored XSSUsing a contributor+ account, access the Meet My Team admin panel and add or edit a team member. Inject a test payload like <script>alert(1)</script> into input fields such as name, role, title, or bio. Save the entry, then view the public team page in the browserAffected if The script tag executes or appears unescaped in the page source when viewing the team page
The environment is affected if Meet My Team plugin version is 2.0.5 or lower and any contributor+ user has access to manage team members in the plugin.
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.
From vendor dataUpdate the Fullworks Meet My Team plugin to a version beyond 2.0.5, which should include proper input validation and output escaping. If no update is available, implement sanitization functions like wp_kses() and esc_html() on user-supplied data before storage and display.
Fix this in Meet My Team
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37339 — 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-2022-37339 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