dbcve.org
Invite AnyoneWordPress extension · Teleogistic

CVE-2024-43327

MEDIUM · 6.1 CVSS v3.1 Published 2024-08-18
Fix available
A fix is available. Upgrade to 1.4.8 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Boone Gorges Invite Anyone allows Reflected XSS.This issue affects Invite Anyone: from n/a through 1.4.7.

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 confidence

A reflected XSS vulnerability in the Boone Gorges Invite Anyone WordPress plugin allows attackers to inject malicious JavaScript through unsanitized user input that gets reflected in the web page without proper output encoding.

MitigationUpdate Invite Anyone plugin to version 1.4.8 or later which includes proper input sanitization and output encoding to prevent XSS attacks.

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
Affected:< 1.4.8

CVSS 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Invite Anyone plugin is installed
    Log into WordPress admin, go to Plugins > Installed Plugins, and look for 'Invite Anyone' by Boone Gorges (also marketed as Teleogistic)
    Affected if Plugin is not found in the plugin list
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find Invite Anyone, and view the version number displayed below the plugin name
    Affected if Version is present but less than 1.4.8
  3. Confirm plugin is active
    In Plugins > Installed Plugins, verify the Invite Anyone plugin shows as 'Active' under its status
    Affected if Plugin is active and version is below 1.4.8
  4. Identify vulnerable code location (optional)
    If you have file access, examine the plugin files for unsanitized $_GET, $_POST, or $_REQUEST parameters that are output via echo or print functions without escaping
    Affected if User input from invite forms or parameters is output without sanitization

You are affected if the Invite Anyone plugin is active and the installed version is below 1.4.8, as the plugin reflects unsanitized user input leading to reflected XSS.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.4.8 or later
Fixed in 1.4.8
Interim mitigation

Update Invite Anyone plugin to version 1.4.8 or later which includes proper input sanitization and output encoding to prevent XSS attacks.

Recommended fix High confidence

1.4.8

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to the WordPress admin dashboard > Plugins page.
  3. 3. Locate the 'Invite Anyone' plugin in the installed plugins list.
  4. 4. Check if an update is available. If not, navigate to Plugins > Add New > Upload Plugin and upload version 1.4.8 of Invite Anyone.
  5. 5. Alternatively, download the latest version (1.4.8) from the WordPress plugin repository or the plugin developer's site.
  6. 6. Deactivate the current version of Invite Anyone plugin.
  7. 7. Delete the current version and install the new version 1.4.8.
  8. 8. Reactivate the plugin and verify functionality.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Invite Anyone Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43327 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-43327 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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