Ninja PopupsWordPress extension · Arscode
CVE-2022-27861
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 · uneditedUnauth. Open Redirect vulnerability in Arscode Ninja Popups plugin <= 4.7.5 versions.
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 confidenceAn unauthenticated open redirect vulnerability exists in the Arscode Ninja Popups WordPress plugin versions 4.7.5 and below. Attackers can craft malicious URLs using the plugin's redirect functionality to redirect users to arbitrary external sites, potentially facilitating phishing 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
Ninja PopupsWordPress extension
<= 4.7.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Arscode Ninja Popups plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Arscode Ninja Popups', or check the /wp-content/plugins/ directory for a folder named ninja-popupsAffected if The plugin is present in the WordPress installation
-
Get the installed plugin versionIn WordPress admin_plugins list, find Ninja Popups and note the version number displayed under the plugin name. Alternatively, open the main plugin file (usually ninja-popups.php) in wp-content/plugins/ninja-popups/ and check the Version header in the plugin comment blockAffected if The version displayed is 4.7.5 or lower
-
Identify if the vulnerable redirect parameter is in useSearch web server access logs (apache/nginx) for requests to your site containing parameters like 'redirect', 'url', or 'target' that point to the ninja-popups plugin endpoint. Common patterns include requests to /?ninja_popups_redirect= or similar. Also check if the plugin's subscribe and redirect features are enabled in the plugin settings under Ninja Popups > General SettingsAffected if The plugin redirect functionality is enabled and exposed to unauthenticated requests with external URLs in redirect parameters
-
Check for suspicious redirect activity in logsReview Apache access.log or Nginx access.log for unusual patterns such as requests containing your domain followed by external domains in redirect parameters, for example: /?np_redirect=http://malicious-site.com or similar constructs using the pluginAffected if Log entries show redirect parameters being used with external URLs pointing to unfamiliar domains
A user is affected if the Arscode Ninja Popups plugin version is 4.7.5 or lower AND the plugin redirect functionality is active and accessible to unauthenticated visitors.
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 Arscode Ninja Popups plugin to a version newer than 4.7.5. If no patched version is available, remove the plugin or implement WAF rules to block suspicious redirect parameters.
Fix this in Ninja Popups
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.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,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27861 — 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-27861 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