Invite AnyoneWordPress extension · Invite Anyone Project
CVE-2017-18545
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 · uneditedThe invite-anyone plugin before 1.3.16 for WordPress has incorrect escaping of untrusted Dashboard and front-end input.
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 confidenceThe invite-anyone WordPress plugin before version 1.3.16 has an XSS (Cross-Site Scripting) vulnerability due to incorrect escaping of untrusted input in both the WordPress Dashboard and front-end areas. This allows attackers to inject malicious scripts through plugin input fields that are not properly sanitized before rendering.
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
Invite AnyoneWordPress extension
< 1.3.16CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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.
-
Locate the Invite Anyone plugin in your WordPress installationCheck your wp-content/plugins directory for a folder named 'invite-anyone' or use the WordPress admin Plugins page to list installed pluginsAffected if The plugin folder or listing exists in your WordPress installation
-
Identify the installed plugin versionOpen the main plugin file (usually invite-anyone/invite-anyone.php) and look for the 'Version:' header in the plugin comments, or check the version in the WordPress admin Plugins pageAffected if The version displayed is lower than 1.3.16 (e.g., 1.3.15, 1.3.14, etc.)
-
Verify the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and confirm the Invite Anyone plugin shows as 'Active'Affected if The plugin is currently active and running on the site
-
Check for user input fields in plugin functionalityNavigate to the plugin settings page (usually under Users > Invite Anyone or a similar admin menu item) and identify any text input fields, invitation form fields, or settings that accept user-provided textAffected if Input fields exist where users can enter custom text (names, emails, messages) that could be rendered without proper escaping
Your environment is affected if the Invite Anyone plugin is installed, active, and running a version lower than 1.3.16, as the plugin contains input fields that render user data without proper escaping.
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 data1.3.16
Update the invite-anyone plugin to version 1.3.16 or later, which contains proper input escaping. If immediate update is not possible, consider disabling the plugin until the patch can be applied.
Fix this in Invite Anyone
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18545 — 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-2017-18545 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