CVE-2026-42733
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in RealMag777 WPCS currency-switcher allows DOM-Based XSS.This issue affects WPCS: from n/a through <= 1.3.1.
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 confidenceDOM-based Cross-site Scripting (XSS) vulnerability in the RealMag777 WPCS currency-switcher plugin allows attackers to inject malicious JavaScript through unsanitized URL parameters that are dynamically inserted into the page DOM without proper output encoding.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 if WPCS currency-switcher plugin is installedCheck your WordPress site's wp-content/plugins directory for a folder named 'wpcs', 'wpcs-currency-switcher', or similar RealMag777 currency-switcher plugin. Alternatively, list installed plugins via WordPress admin under Plugins.Affected if The RealMag777 WPCS currency-switcher plugin is present on the WordPress site
-
Determine the installed plugin versionIf the plugin is installed, locate the main plugin file (usually wpcs.php or similar) and open it to find the version declaration in the plugin header comment, or check the version in the WordPress plugin repository if installed from there.Affected if The version cannot be determined or is older than any available patched version; treat unknown versions as potentially vulnerable
-
Verify if URL parameters are processed and reflected in the pageVisit pages on the site with arbitrary URL parameters such as ?currency=test or ?wpcs_param=<script>alert(1)</script>. View the page source or use browser developer tools to inspect the DOM and see if the parameter values appear unescaped in the HTML.Affected if URL parameter values are directly inserted into the DOM without HTML encoding (visible as raw <script> tags or unescaped characters like < > " in the DOM)
-
Inspect the plugin source code for unsafe DOM manipulationExamine the main plugin PHP files for functions that retrieve $_GET or $_REQUEST parameters and output them via echo, print, or JavaScript without using esc_html(), esc_attr(), or similar WordPress escaping functions.Affected if Code directly outputs $_GET or $_REQUEST values into HTML or JavaScript without sanitization functions
If the RealMag777 WPCS currency-switcher plugin is installed and URL parameters are reflected in the page DOM without HTML encoding, the environment is affected by this DOM-based XSS vulnerability.
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 dataApply proper output escaping when inserting data into the DOM; use safe DOM manipulation methods that automatically escape content or explicitly sanitize all user-controlled input before rendering.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42733 — 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-2026-42733 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