CVE-2026-32362
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 · uneditedMissing Authorization vulnerability in activity-log.com WP Sessions Time Monitoring Full Automatic activitytime allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Sessions Time Monitoring Full Automatic: from n/a through <= 1.1.3.
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 confidenceA Missing Authorization vulnerability in the WordPress plugin 'WP Sessions Time Monitoring Full Automatic' allows unauthenticated attackers to access sensitive functionality or data due to missing capability checks and access controls on certain plugin endpoints or functions. This broken access control issue enables exploitation of incorrectly configured security levels.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 the plugin is installedCheck your WordPress site's wp-content/plugins/ directory for a folder named 'wp-sessions-time-monitoring-full-automatic' or search for the plugin in the WordPress admin under Plugins > Installed PluginsAffected if The plugin 'WP Sessions Time Monitoring Full Automatic' appears in your installation
-
Identify the installed plugin versionOpen the main plugin PHP file (usually wp-content/plugins/wp-sessions-time-monitoring-full-automatic/*.php) and look for a version comment or define statement like 'define( "VERSION", "x.x.x" );'Affected if You cannot determine the version or are running any version of this plugin since no patched version is specified
-
Test for unauthenticated endpoint accessUsing a tool like curl or Burp Suite, send requests to common WordPress admin-ajax.php or plugin-specific endpoints (e.g., ?action=wpstm_* or similar) WITHOUT providing any authentication cookies or credentialsAffected if The endpoints return successful data or execute actions without requiring login or capability verification
-
Inspect plugin capability checksReview the plugin's PHP files for function calls like current_user_can(), wp_verify_nonce(), or check_admin_referer() on sensitive operations; grep for these patterns across the plugin directoryAffected if Sensitive functions lack capability checks or the nonce verification is missing/disabled on admin actions
-
Review access control on plugin functionsExamine the plugin's AJAX handlers and direct-access functions in the main plugin file; check if they properly validate user permissions before processing requestsAffected if The plugin executes operations for unauthenticated users or lacks role-based access restrictions
Your environment is affected if the plugin is installed and its endpoints or functions can be accessed or executed without authentication or capability verification.
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 dataUpdate the plugin to the latest patched version once available. Until then, restrict access to the plugin through web server configuration or consider disabling the plugin if unauthorized access is observed.
- Consultation2.0 h
- Implementation6.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 $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32362 — 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-2026-32362 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