SeoWordPress extension · 10web
CVE-2023-34375
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 10Web SEO by 10Web plugin <= 1.2.9 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 confidenceUnauthenticated reflected cross-site scripting (XSS) vulnerability in the 10Web SEO by 10Web WordPress plugin version 1.2.9 and below allows attackers to inject malicious JavaScript through vulnerable parameters that are reflected back to users 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
SeoWordPress extension
<= 1.2.9CVSS 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 10Web SEO plugin is installedLog into WordPress admin panel, navigate to Plugins > Installed Plugins, and search for '10web SEO' or '10Web SEO' in the plugin listAffected if The plugin is not found in the installed plugins list, then the environment is not affected
-
Check the installed version of 10Web SEOIn the WordPress admin under Plugins > Installed Plugins, locate the 10Web SEO plugin and read the version number displayed below the plugin nameAffected if The installed version is 1.2.9 or lower, indicating the vulnerable version is present
-
Confirm plugin status is activeIn the WordPress plugins list, verify whether 10Web SEO shows as 'Active' under the plugin status columnAffected if The plugin is active and the version is 1.2.9 or below, the vulnerability is present and exploitable
-
Inspect plugin files for vulnerable code patternsAccess the plugin directory via file manager or FTP (typically at wp-content/plugins/seo-by-10web/), and examine PHP files for unsanitized use of request parameters such as $_GET or $_POST that are output without escapingAffected if Unsanitized reflection of user input is found in the plugin code, confirming the XSS vulnerability exists
The environment is affected if the 10Web SEO plugin is installed, active, and running version 1.2.9 or lower, as this version contains the unauthenticated reflected XSS flaw.
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 10Web SEO plugin to the latest version (after 1.2.9) to receive the security patch, or remove the plugin until an update is available. Additionally, implement web application firewall (WAF) rules to block XSS attack patterns as a temporary protective measure.
Fix this in Seo
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34375 — 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-34375 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