Stock TickerWordPress extension · Urosevic
CVE-2022-45365
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Aleksandar Urošević Stock Ticker allows Reflected XSS.This issue affects Stock Ticker: from n/a through 3.23.2.
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 confidenceReflected XSS vulnerability in the Stock Ticker plugin allows attackers to inject malicious JavaScript through unsanitized user input that gets reflected in web pages without proper output encoding. The vulnerability exists in versions up to and including 3.23.2.
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
Stock TickerWordPress extension
<= 3.23.2CVSS 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 Stock Ticker plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Stock Ticker' or 'Urosevic Stock Ticker' in the list. Note whether it is activated or not.Affected if Plugin is installed and activated on the WordPress site
-
Check installed version numberIn the Plugins list, click on the plugin name or view details to find the version number displayed (e.g., 'Version 3.23.2' or lower). Compare this to the affected range <= 3.23.2.Affected if Installed version is 3.23.2 or any lower version number
-
Identify usage of plugin shortcodes or widgetsCheck pages, posts, or widget areas for the presence of [stock_ticker] shortcode or Stock Ticker widget being used. This can be done by viewing page content in admin or inspecting source of public pages.Affected if Plugin shortcode [stock_ticker] or widget is actively used on public-facing pages
-
Test for reflected XSS in URL parametersVisit a page using Stock Ticker and observe if any URL parameters (such as ticker symbols, search terms, or custom text) are reflected in the HTML output without encoding. Inspect page source to see if user input appears as raw text within HTML tags.Affected if User-supplied input in URL parameters is reflected in HTML output without proper encoding (visible as unescaped characters like < or >)
-
Check plugin settings for unsanitized input fieldsGo to Stock Ticker settings page (Settings > Stock Ticker) and examine any text fields where user input is accepted. Save a test value with special characters and view the frontend to see if those characters are rendered safely or as raw HTML.Affected if Input containing <script> or similar HTML tags is rendered as-is in browser without being encoded to <script>
A user is affected if the Stock Ticker plugin version is 3.23.2 or lower AND the plugin is installed and actively used on public pages where user input is reflected without encoding.
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 dataUpgrade to a patched version of Stock Ticker that properly sanitizes and encodes all user-supplied input before reflecting it in HTML output. If no patch available, implement input validation and output encoding at the application boundary.
Fix this in Stock Ticker
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45365 — 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-2022-45365 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