Pop UpWordPress extension · Mypopups
CVE-2022-38070
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 · uneditedPrivilege Escalation (subscriber+) vulnerability in Pop-up plugin <= 1.1.5 at WordPress.
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 confidenceThe Pop-up WordPress plugin versions 1.1.5 and below contains a privilege escalation vulnerability that allows authenticated users with subscriber-level permissions to elevate their privileges to higher administrative levels.
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
Pop UpWordPress extension
<= 1.1.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify Pop-up plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Mypopups Pop Up' or 'Pop-up' in the list of active pluginsAffected if The plugin appears in the installed plugins list and is activated
-
Check installed plugin versionIn the plugins list, click on the plugin to view details, or inspect the plugin header in wp-content/plugins/mypopups/ folder for the Version fieldAffected if The version number is 1.1.5 or lower (e.g., 1.1.5, 1.1.4, 1.1.0, etc.)
-
Identify subscriber-level user accountsIn WordPress admin, go to Users and review the list for any accounts with the Subscriber roleAffected if At least one user account with Subscriber role exists on the site
-
Check for privilege escalation attack indicatorsReview user role changes in the audit log, or compare current user roles against known role assignments - look for subscribers who suddenly have Administrator capabilitiesAffected if Subscriber accounts have been granted elevated privileges (Administrator, Editor, or Author roles) without manual admin intervention
The environment is affected if the Mypopups Pop Up plugin version 1.1.5 or below is installed and active, and subscriber-level user accounts exist who could have been escalated to administrative 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.
dbcve · scopedUpdate the Pop-up plugin to the latest version immediately, or deactivate and remove the plugin if no patched version is available.
Pop Up plugin version 1.1.6 or later (latest available version)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the 'Pop Up' plugin in the list
- 4. If an update is available, click 'Update Now' to upgrade to the latest fixed version
- 5. Alternatively, download the latest version from wordpress.org and upload it via Plugins > Add New > Upload Plugin
- 6. After updating, verify the plugin version is greater than 1.1.5
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Pop Up
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-2022-38070 — 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-38070 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