Mobile Browser Color SelectWordPress extension · Script
CVE-2022-1969
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 · uneditedThe Mobile browser color select plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.0.1. This is due to missing or incorrect nonce validation on the admin_update_data() function. This makes it possible for unauthenticated attackers to inject malicious web scripts via forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 · high confidenceThe Mobile browser color select WordPress plugin fails to validate nonces in the admin_update_data() function, allowing unauthenticated attackers to forge requests that trick administrators into executing the function. This CSRF vulnerability can lead to stored XSS injection if the attacker convinces a logged-in admin to click a malicious link.
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
Mobile Browser Color SelectWordPress extension
<= 1.0.1CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Confirm plugin installation and versionCheck if Script Mobile Browser Color Select plugin is installed in WordPress and note the installed version numberAffected if The installed version is 1.0.1 or lower
-
Locate the vulnerable function fileAccess the plugin directory (typically wp-content/plugins/script-mobile-browser-color-select/) and locate the file containing the admin_update_data() functionAffected if The file exists and contains admin_update_data() function
-
Inspect nonce validation in admin_update_data()Open the file containing admin_update_data() and search for check_admin_referer() or wp_verify_nonce() calls at the beginning of the function before any data processingAffected if No nonce validation is found - the function processes data without verifying request authenticity
-
Check for stored XSS vulnerabilityReview how the function handles and stores admin-submitted data (such as plugin settings or color values) and whether it uses sanitization functions like esc_html() or esc_attr() when outputting data in admin pagesAffected if Data is stored and displayed without proper sanitization, allowing injected scripts to persist
The environment is affected if the Script Mobile Browser Color Select plugin version is 1.0.1 or lower AND the admin_update_data() function lacks nonce validation using check_admin_referer() or wp_verify_nonce().
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 plugin to the latest version and ensure admin_update_data() implements proper nonce validation using check_admin_referer() or wp_verify_nonce() before processing any data.
Fix this in Mobile Browser Color Select
Scoped from the published advisory
- Consultation1.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1969 — 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-1969 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