Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.1amended

Moderate severity vulnerability that affects total.js

CVE-2019-10260GHSA-72p5-2r6g-fm6v

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (total.js 3.3.0-13), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm total.js

    Affected
    <= 3.3.0-12
    Fixed in
    3.3.0-13

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.1 · CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
EPSS
  • CVE-2019-10260: 0.91% estimated exploitation activity in the next 30 days; percentile 59.86 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Total.js CMS 12.0.0 has XSS related to themes/admin/views/index.html (item.message) and themes/admin/public/ui.js (column.format).

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-72p5-2r6g-fm6v

  2. Revision 1 · created ·

    Published from osv record GHSA-72p5-2r6g-fm6v

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2019-10260

Advisory: Moderate severity vulnerability that affects total.js
IDs: CVE-2019-10260, GHSA-72p5-2r6g-fm6v
Record: https://patchnext.com/advisories/cve-2019-10260 (revision 2, source checked 26 Oct 2026, 12:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: total.js 3.3.0-13. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm total.js: affected <= 3.3.0-12; fixed in 3.3.0-13

## Suggested inspection (read-only)
- `npm ls total.js --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on total.js.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-72p5-2r6g-fm6v (OSV record GHSA-72p5-2r6g-fm6v lists affected ranges: npm total.js >=0 <3.3.0-13 (fixed))
- Verified: https://github.com/advisories/GHSA-72p5-2r6g-fm6v (GitHub-reviewed advisory GHSA-72p5-2r6g-fm6v lists affected ranges: npm total.js >=0 <=3.3.0-12)

Commands are suggestions: review each one before running it.

Loading voting…