Webmaster ToolsWordPress extension · Lionscripts
CVE-2023-46092
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in LionScripts.Com Webmaster Tools allows Stored XSS.This issue affects Webmaster Tools: from n/a through 2.0.
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 confidenceA CSRF vulnerability in LionScripts.Com Webmaster Tools allows attackers to craft malicious requests that result in stored XSS. An attacker can trick an authenticated admin into visiting a specially crafted page, causing the browser to silently submit a request that injects malicious scripts into the application, which are then stored and executed when other users view the affected content.
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
Webmaster ToolsWordPress extension
<= 2.0CVSS 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.
-
Identify Lionscripts Webmaster Tools installationLocate the Lionscripts Webmaster Tools installation in your web server directories and confirm the product name in the application files or admin interfaceAffected if The product is present and appears to be Lionscripts Webmaster Tools
-
Determine installed versionCheck the application version information, typically found in the admin panel, an about page, or version metadata file within the product installation directoryAffected if The installed version is 2.0 or lower (any version <= 2.0)
-
Verify admin authentication is in useConfirm that the web application has an authenticated admin area and that administrative functions are accessible after loginAffected if The admin interface is accessible and requires authentication for state-changing operations
-
Inspect state-changing endpoints for CSRF protectionExamine the application's forms or API endpoints that perform state-changing operations (such as content management or settings updates) and check if they include anti-CSRF tokens or referrer validationAffected if State-changing operations lack anti-CSRF tokens or do not validate request origins
-
Test input handling for XSS sanitizationSubmit potentially malicious script payloads through the application's input fields and verify whether proper input validation or output encoding is applied before storage and displayAffected if User-supplied input is stored and rendered without sanitization or encoding, allowing script injection
You are affected if Lionscripts Webmaster Tools version 2.0 or lower is installed and the application lacks CSRF protection on state-changing operations combined with insufficient input validation that allows stored XSS execution.
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 dataImplement anti-CSRF tokens for state-changing operations and apply proper input validation combined with context-aware output encoding to prevent the stored XSS from executing.
Fix this in Webmaster Tools
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46092 — 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-46092 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