Wp Chinese ConversionWordPress extension · Wpplugins
CVE-2023-32518
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in Ono Oogami WP Chinese Conversion plugin <= 1.1.16 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 confidenceAn unauthenticated reflected cross-site scripting (XSS) vulnerability exists in the Ono Oogami WP Chinese Conversion WordPress plugin versions 1.1.16 and prior. Attackers can inject malicious JavaScript through crafted URLs that get reflected back in the application's response without proper sanitization or output encoding.
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
Wp Chinese ConversionWordPress extension
<= 1.1.16CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedCheck the WordPress plugins directory for 'wp-chinese-conversion' or 'oogami-wp-chinese-conversion' folder, or list installed plugins via wp-cli: wp plugin list --status=active --format=csvAffected if The plugin folder or listing shows the Ono Oogami WP Chinese Conversion plugin is present and active
-
Determine the installed versionRead the plugin's main PHP file header for the Version field, or run: wp plugin get wp-chinese-conversion --field=versionAffected if The version number returned is 1.1.16 or lower
-
Confirm the plugin is activeCheck if the plugin status is 'active' in WordPress admin plugins page or via wp-cli: wp plugin is-active wp-chinese-conversionAffected if The plugin is active and accessible to unauthenticated users
-
Verify the vulnerable parameter is reachableCheck if the plugin registers any public-facing URL parameters, typically in the plugin's main PHP file by searching for $_GET, $_REQUEST, or add_query_arg usageAffected if The plugin handles URL parameters without sanitization and reflects them in output
The environment is affected if the Ono Oogami WP Chinese Conversion plugin version 1.1.16 or lower is installed and active, allowing unauthenticated users to access the vulnerable reflected XSS endpoint.
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 once a patch is released, or deactivate and remove the plugin until a fix is available. Users should avoid clicking untrusted links to the affected site.
Fix this in Wp Chinese Conversion
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32518 — 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-32518 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