Ltl Freight QuotesWordPress extension · Eniture

CVE-2025-22284

MEDIUM · 6.1 CVSS v3.1 Published 2025-02-16
Fix available
A fix is available. Upgrade to 2.5.9 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in enituretechnology LTL Freight Quotes – Unishippers Edition ltl-freight-quotes-unishippers-edition allows Reflected XSS.This issue affects LTL Freight Quotes – Unishippers Edition: from n/a through <= 2.5.8.

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

Reflected XSS vulnerability in the enituretechnology LTL Freight Quotes – Unishippers Edition WordPress plugin allows attackers to inject malicious JavaScript through unsanitized user input that gets reflected back in generated web pages, potentially leading to session hijacking or credential theft.

MitigationUpdate the plugin to a version greater than 2.5.8 which contains the security patch, or implement proper input sanitization and output encoding on all user-supplied parameters before reflecting them in HTML.

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
Ltl Freight QuotesWordPress extension
Affected:< 2.5.9

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
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 checks

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

  1. Identify plugin installation and version
    Access the WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'Eniture LTL Freight Quotes' or 'Unishippers Edition', and note the version number displayed. Alternatively, use WP-CLI: `wp plugin list --path=/path/to/wordpress | grep -i unishippers`
    Affected if The plugin is installed and the version displayed is lower than 2.5.9
  2. Verify plugin is active
    In WordPress admin under Plugins > Installed Plugins, confirm the plugin shows as 'Active'. Alternatively, run: `wp plugin is-active eniture-ltl-freight-quotes-unishippers-edition --path=/path/to/wordpress`
    Affected if The plugin is active and the version is below 2.5.9
  3. Check main plugin file for version header
    Locate the main plugin PHP file (typically in wp-content/plugins/eniture-ltl-freight-quotes-unishippers-edition/) and inspect the file header comment for the 'Version:' field
    Affected if The version in the plugin file header is below 2.5.9

If the Eniture LTL Freight Quotes plugin is installed, active, and its version is below 2.5.9, the environment is affected by this reflected XSS vulnerability.

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 2.5.9 or later
Fixed in 2.5.9
Interim mitigation

Update the plugin to a version greater than 2.5.8 which contains the security patch, or implement proper input sanitization and output encoding on all user-supplied parameters before reflecting them in HTML.

Recommended fix Moderate confidence

2.5.9

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the 'LTL Freight Quotes – Unishippers Edition' plugin
  4. Click 'Update now' or 'Update' to install version 2.5.9
  5. Alternatively, use WP-CLI: wp plugin update ltl-freight-quotes-unishippers-edition
  6. After updating, clear any caching plugins and browser cache
  7. Test the plugin functionality to ensure the LTL freight quote features work correctly
  8. Verify the XSS vulnerability is resolved by confirming user inputs are properly sanitized

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

Fix this in Ltl Freight Quotes Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22284 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-22284 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