Wpmobile.appWordPress extension · Amauri
CVE-2023-22702
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 · uneditedAuth. (contributor+) Cross-Site Scripting (XSS) vulnerability in WPMobile.App WPMobile.App — Android and iOS Mobile Application plugin <= 11.13 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 confidenceAuthenticated users with contributor-level or higher privileges can inject malicious scripts via a cross-site scripting vulnerability in the WPMobile.App WordPress plugin for Android/iOS mobile applications. The vulnerability exists in versions 11.13 and below, allowing attackers to execute arbitrary JavaScript in the context of the affected application.
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
Wpmobile.appWordPress extension
< 11.14CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify WPMobile.App plugin versionNavigate to WordPress admin dashboard > Plugins > Installed Plugins, locate WPMobile.App (or Amauri Wpmobile.app), and note the installed version numberAffected if The installed version is 11.13 or lower (versions below 11.14)
-
Confirm plugin is activeIn the WordPress Plugins page, verify that the WPMobile.App plugin shows as ActiveAffected if The plugin is installed and activated on the WordPress site
-
Check for elevated user accountsGo to WordPress admin > Users > All Users and review account roles. The vulnerability requires at least one user with Contributor, Author, Editor, or Administrator roleAffected if Any user account with contributor-level or higher privileges exists on the site
You are affected if WPMobile.App version 11.13 or below is installed and active on your WordPress site, and your site has at least one user with contributor-level or higher access.
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 · scoped11.14
Update the WPMobile.App plugin to the latest version beyond 11.13, and implement proper input sanitization and output encoding on all user-supplied data within the plugin.
WPMobile.App version 11.14 or later
- 1. Backup your WordPress site before making any changes
- 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
- 3. Find the WPMobile.App plugin (WPMobile.App — Android and iOS Mobile Application)
- 4. If an update is available, click 'Update Now' to upgrade to version 11.14 or later
- 5. After updating, verify the plugin is running version 11.14 or higher by checking the plugins list
- 6. Test that the plugin functionality works as expected
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wpmobile.app
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22702 — 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-2023-22702 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