CVE-2026-107648

validated

GHSA-fg5j-28g4-3v66 ↗EUVD-2026-102843 ↗

check availablenot proven exploitable

cve.orgpublic pockev

switcorp WP Sessions Time Monitoring Full Automatic <= 1.1.5

CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

ETK-2026-2270, permanent identifier

cvss7.2cna vendorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

+4.6dTTV

<1mAI analysis

Check if you are vulnerable

timeline

0 = trigger signal

trigger signal (cve.org) +0dcheck available+4.6dagent stopped

+1d

+2d

+3d

+4d

+5d

description

WP Sessions Time Monitoring Full Automatic versions through 1.1.5 are affected by stored cross-site scripting. An unauthenticated attacker may place script content that runs in another user's browser when that user views the affected page.

mitigation

Disable and remove the plugin from WordPress sites until a maintained release that addresses the issue is available. Restrict public access to affected sites as an additional exposure-reduction measure.

check

available

exploit

automation

deterministic

auth required

EPSS

–

agent run time

<1m

cve.org record, t = 0

2026-10-16 11:28Z

Δ to public poc

–

Δ to kev

–

outcome

Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

2026-10-16 11:28Z
cve_org: trigger signal, started the run
https://www.cve.org/CVERecord?id=CVE-2026-107648
2026-10-21 02:46Z
Patchstack ships a detection
patchstack · https://patchstack.com/database/vulnerability/activitytime/wordpress-wp-sessions-time-monitoring-full-automatic-plugin-1-1-5-unauthenticated-stored-cross-site-scripting-vulnerability?_a_id=500

this entry in the feed

GET /api/v1/feed/CVE-2026-107648

{
  "etk_id": "ETK-2026-2270",
  "cve_id": "CVE-2026-107648",
  "display_id": "CVE-2026-107648",
  "ghsa_id": "GHSA-fg5j-28g4-3v66",
  "euvd_id": "EUVD-2026-102843",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stored cross-site scripting in WP Sessions Time Monitoring",
  "summary": "WP Sessions Time Monitoring Full Automatic versions through 1.1.5 are affected by stored cross-site scripting. An unauthenticated attacker may place script content that runs in another user's browser when that user views the affected page.",
  "mitigation": "Disable and remove the plugin from WordPress sites until a maintained release that addresses the issue is available. Restrict public access to affected sites as an additional exposure-reduction measure.",
  "vendor": "switcorp",
  "product": "WP Sessions Time Monitoring Full Automatic",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.1.5"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "WP Sessions Time Monitoring Full Automatic",
      "purl": null
    }
  ],
  "cwes": [
    79
  ],
  "cvss_score": 7.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.010868016666666667,
  "t0_at": "2026-10-16T11:28:51.492000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-21T02:46:05.253224+00:00",
      "days": 4.6369648289814815,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T11:28:51.492000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-16T11:28:51.492000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T11:28:51.492000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-107648"
    }
  }
}

published 2026-10-21 02:46Z
last change 2026-10-21 03:26Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.