dbcve.org
LoggedinWordPress extension · Duckdev

CVE-2024-9228

MEDIUM · 6.1 CVSS v3.1 Published 2024-10-01
Fix available
A fix is available. Upgrade to 1.3.2 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
The Loggedin – Limit Active Logins plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg without appropriate escaping on the URL in all versions up to, and including, 1.3.1. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. This is only exploitable when the leave a review notice is present.

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

The Loggedin – Limit Active Logins WordPress plugin uses add_query_arg() without proper escaping, creating a reflected XSS vulnerability. This flaw is only exploitable when the 'leave a review' admin notice is present, allowing unauthenticated attackers to inject malicious scripts via crafted URLs that trick administrators into clicking them.

MitigationUpdate the plugin to the latest version (beyond 1.3.1) to obtain the patched code, or disable the plugin if no update is available. Until patched, warn administrators not to click untrusted links while the review notice is visible.

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
LoggedinWordPress extension
Affected:< 1.3.2

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 plugin is installed
    Check if the Loggedin - Limit Active Logins plugin is installed on the WordPress site. This can be done via WordPress admin under Plugins > Installed Plugins, or by checking the /wp-content/plugins/ directory for a folder named 'loggedin' or similar.
    Affected if The plugin is not installed.
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and look for the version number listed under the Loggedin - Limit Active Logins plugin. Alternatively, check the plugin's main PHP file for the 'Version' header in the plugin comment block.
    Affected if The installed version is lower than 1.3.2.
  3. Identify if review notice is active
    Log into the WordPress admin dashboard and look for a 'leave a review' or similar promotional notice from the Loggedin plugin. This notice typically appears at the top of admin pages. Check both the main plugin settings page and the WordPress plugin list page.
    Affected if The 'leave a review' admin notice from this plugin is currently visible to administrators.
  4. Inspect admin URLs for reflected parameters
    When logged in as an administrator, examine the URL parameters in the browser address bar while navigating admin pages where the Loggedin plugin notice appears. Look for query parameters that might be reflected without proper escaping, particularly any parameters that could contain user-supplied input.
    Affected if URLs contain unexpected or suspicious query parameters that appear unescaped when the plugin notice is displayed.

A user is affected if the Loggedin - Limit Active Logins plugin version is below 1.3.2 AND the 'leave a review' admin notice from this plugin is currently visible to administrators in the WordPress admin area.

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.3.2 or later
Fixed in 1.3.2
Interim mitigation

Update the plugin to the latest version (beyond 1.3.1) to obtain the patched code, or disable the plugin if no update is available. Until patched, warn administrators not to click untrusted links while the review notice is visible.

Recommended fix High confidence

1.3.2

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Loggedin – Limit Active Logins' plugin
  4. 4. Check the current version installed (should be 1.3.1 or below)
  5. 5. Click 'Update Now' if an update to version 1.3.2 is available, or manually update by downloading version 1.3.2 from the WordPress plugin repository
  6. 6. Verify the update was successful by confirming the plugin now shows version 1.3.2 or higher

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

Fix this in Loggedin Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9228 — 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-9228 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