Invite AnyoneWordPress extension · Teleogistic
CVE-2017-6955
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 · uneditedAn issue was discovered in by-email/by-email.php in the Invite Anyone plugin before 1.3.15 for WordPress. A user is able to change the subject and the body of the invitation mail that should be immutable, which facilitates a social engineering attack.
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.15 contains an authorization flaw in by-email/by-email.php where the invitation email subject and body are mutable by users rather than being fixed/immutable as intended. An attacker with privileges to send invitations can modify the email content to craft socially engineered messages, tricking recipients into trusting malicious links or instructions.
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.13CVSS 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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Check if Invite Anyone plugin is installedNavigate to WordPress admin > Plugins and look for 'Invite Anyone' or inspect the wp-content/plugins/ directory for an 'invite-anyone' folderAffected if The plugin is not found or the folder does not exist - you are not affected
-
Determine installed plugin versionOpen the main plugin file (usually invite-anyone/readme.txt or invite-anyone/invite-anyone.php) and locate the version number in the header commentAffected if Version is 1.3.13 or lower - you are running a vulnerable version
-
Verify vulnerable file existsCheck if the file wp-content/plugins/invite-anyone/by-email/by-email.php exists on the serverAffected if File exists and plugin version is <=1.3.13 - the vulnerable code is present
-
Confirm by-email invitation feature is enabledIn WordPress admin, go to Invite Anyone plugin settings and verify the 'by-email' invitation method is active/enabledAffected if By-email invitations are enabled - users can potentially exploit the flaw
-
Identify users with invitation privilegesCheck WordPress user roles or plugin settings to see which users have the ability to send invitationsAffected if Multiple users or untrusted users have invitation privileges - the attack surface exists
You are affected if the Invite Anyone plugin version is 1.3.13 or lower, the by-email/by-email.php file exists, and the by-email invitation feature is enabled with users who have invitation privileges.
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 dataUpgrade the Invite Anyone plugin to version 1.3.15 or later. Until then, restrict invitation privileges to highly trusted users and monitor for suspicious invitation activity.
Fix this in Invite Anyone
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6955 — 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-6955 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