dbcve.org
Traffic ManagerWordPress extension · Sedlex

CVE-2022-42460

MEDIUM · 5.4 CVSS v3.1 Published 2022-11-10
Fix available
A fix is available. Upgrade to after 1.4.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Broken Access Control vulnerability leading to Stored Cross-Site Scripting (XSS) in Traffic Manager plugin <= 1.4.5 on WordPress.

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

Broken Access Control in the Traffic Manager plugin for WordPress (versions 1.4.5 and below) allows authenticated attackers to inject and store malicious JavaScript code through insufficient validation of user inputs. This stored XSS executes when other users access the affected functionality, potentially compromising admin sessions or stealing credentials.

MitigationUpdate the Traffic Manager plugin to a version newer than 1.4.5. If no patched version is available, remove the plugin entirely and seek an alternative traffic management solution.

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
Traffic ManagerWordPress extension
Affected:<= 1.4.5

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Identify if Sedlex Traffic Manager plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'traffic-manager', 'sedlex-traffic-manager', or similar.
    Affected if The plugin folder exists in the WordPress plugins directory.
  2. Determine the installed plugin version
    In WordPress admin, locate the plugin in the Plugins list and view the version number displayed beneath the plugin name. Alternatively, open the main plugin PHP file (e.g., traffic-manager.php or sedlex-traffic-manager.php) and check the 'Version' header in the plugin comment block.
    Affected if The displayed version is 1.4.5 or lower.
  3. Confirm the plugin is active
    In WordPress admin > Plugins, check if the plugin shows as 'Active' rather than 'Inactive' or 'Network Deactivated'.
    Affected if The plugin is currently activated on the WordPress site.
  4. Verify user account existence
    Check WordPress admin > Users to confirm that user accounts exist on the site, particularly any subscriber-level or contributor-level accounts that could potentially submit content exploited by this stored XSS.
    Affected if Any authenticated user accounts exist on the WordPress site.

A user is affected if the Sedlex Traffic Manager plugin version 1.4.5 or lower is installed and active on their WordPress site, enabling an authenticated attacker to inject stored XSS payloads.

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.4.5
Interim mitigation

Update the Traffic Manager plugin to a version newer than 1.4.5. If no patched version is available, remove the plugin entirely and seek an alternative traffic management solution.

Recommended fix Moderate confidence

Traffic Manager version 1.4.6 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Traffic Manager plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.4.6 or later
  5. 5. Alternatively, download the latest version from wordpress.org and upload it via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is working correctly

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

Fix this in Traffic Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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