dbcve.org
Mshop My SiteWordPress extension · Codemshop

CVE-2023-47243

HIGH · 8.8 CVSS v3.1 Published 2023-11-18
Fix available
A fix is available. Upgrade to after 1.1.6 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Cross-Site Request Forgery (CSRF) vulnerability in CodeMShop 코드엠샵 마이사이트 – MSHOP MY SITE.This issue affects 코드엠샵 마이사이트 – MSHOP MY SITE: from n/a through 1.1.6.

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 confidence

This is a Cross-Site Request Forgery (CSRF) vulnerability in the CodeMShop MSHOP MY SITE WordPress plugin/theme affecting versions up to 1.1.6. The flaw allows attackers to trick authenticated users into performing unintended actions by sending malicious requests, potentially leading to unauthorized configuration changes or data manipulation within the affected application.

MitigationImplement anti-CSRF tokens (nonce verification) on all state-changing operations including forms and AJAX requests, and ensure proper referer/origin header validation. Upgrade to the latest version if a patch is available.

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
Mshop My SiteWordPress extension
Affected:<= 1.1.6

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

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

  1. Verify if CodeMShop Mshop My Site is installed
    Check the WordPress plugins directory (wp-content/plugins/) or themes directory (wp-content/themes/) for a folder named 'mshop-my-site', 'codemshop', or similar. Alternatively, log into the WordPress admin dashboard and navigate to Plugins or Appearance > Themes to list installed items.
    Affected if The plugin or theme folder is present in the WordPress installation
  2. Confirm the exact version number
    If the plugin is installed, open the main PHP file (usually named mshop-my-site.php or similar in the plugin folder) and locate the 'Version' header in the plugin comments at the top. For a theme, check style.css for the 'Version' comment.
    Affected if The version is 1.1.6 or lower (any version up to and including 1.1.6)
  3. Check if the plugin/theme is active on the site
    In WordPress admin, go to Plugins > Installed Plugins and verify whether CodeMShop Mshop My Site shows as 'Active'. For themes, check Appearance > Themes to see if it is the active theme.
    Affected if The plugin or theme is currently active and the version is vulnerable

If CodeMShop Mshop My Site (plugin or theme) is installed and active at version 1.1.6 or lower, the site is affected by this CSRF 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.1.6
Interim mitigation

Implement anti-CSRF tokens (nonce verification) on all state-changing operations including forms and AJAX requests, and ensure proper referer/origin header validation. Upgrade to the latest version if a patch is available.

Recommended fix Moderate confidence

Latest version of Mshop My Site past 1.1.6 (check WordPress plugin repository for current stable release)

  1. 1. Check the current version of the Mshop My Site (코드엠샵 마이사이트 – MSHOP MY SITE) plugin installed on your WordPress site
  2. 2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. 3. If an update is available for Mshop My Site, update to the latest version
  4. 4. If no update is available through WordPress, check the official WordPress plugin repository or CodeMShop's website for the latest patched version
  5. 5. After updating, verify the plugin is functioning correctly on your site
  6. 6. Consider implementing additional CSRF protections at the server level (e.g., ensuring SameSite cookies are used for authentication)
Caveat Review plugin changelog for any breaking changes between your current version and the new version

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

Fix this in Mshop My Site Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47243 — 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-47243 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