dbcve.org
Responsive Column WidgetsWordPress extension · Michaeluno

CVE-2023-47520

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to after 1.2.7 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Michael Uno (miunosoft) Responsive Column Widgets plugin <= 1.2.7 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 · high confidence

Unauthenticated reflected Cross-Site Scripting (XSS) vulnerability in the Responsive Column Widgets WordPress plugin versions 1.2.7 and below allows attackers to inject malicious scripts via unsanitized input that gets reflected back in the HTTP response.

MitigationUpdate the Responsive Column Widgets plugin to the latest version once a patch is released. Until then, disable the plugin or implement WAF rules to block XSS attack patterns in requests.

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
Responsive Column WidgetsWordPress extension
Affected:<= 1.2.7

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Responsive Column Widgets plugin is installed
    Navigate to WordPress admin Dashboard > Plugins > Installed Plugins and look for 'Michaeluno Responsive Column Widgets' in the list
    Affected if The plugin appears in the installed plugins list
  2. Verify the installed plugin version
    Click on the plugin name or view details to see the version number displayed (e.g., 'Version 1.2.7' or lower)
    Affected if The version shown is 1.2.7 or any version lower (e.g., 1.2.6, 1.2.5, etc.)
  3. Confirm the plugin is active
    In the Plugins list, verify the plugin has a 'Active' status beneath its name (as opposed to 'Inactive' or 'Network Active')
    Affected if The plugin is currently activated on the site
  4. Identify accessible endpoints handling unsanitized input
    Review plugin files (typically in wp-content/plugins/responsive-column-widgets/) for any GET/POST parameter handling that reflects user input back into HTML output without sanitization (functions like echo, print, or PHP output statements using request parameters)
    Affected if The plugin code reflects request parameters directly into page output without proper escaping (esc_html, esc_attr, etc.)

You are affected if the Responsive Column Widgets plugin is installed, active, and running version 1.2.7 or lower, as this version contains the unsanitized input reflection vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.2.7
Interim mitigation

Update the Responsive Column Widgets plugin to the latest version once a patch is released. Until then, disable the plugin or implement WAF rules to block XSS attack patterns in requests.

Recommended fix Moderate confidence

1.2.8

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Responsive Column Widgets plugin
  4. 4. Check the current installed version (should be <= 1.2.7)
  5. 5. Click 'Update Now' if an update is available, or manually download version 1.2.8 from the WordPress plugin repository
  6. 6. Verify the plugin is updated to version 1.2.8 or higher
  7. 7. Test the plugin functionality on the frontend to ensure the update did not break existing features

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Responsive Column Widgets Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47520 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-47520 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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