CVE-2025-31375
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in bhoogterp Scheduled scheduled allows Stored XSS.This issue affects Scheduled: from n/a through <= 1.0.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the bhoogterp Scheduled plugin allows attackers to trick authenticated users into performing unintended actions that result in Stored XSS. The lack of anti-CSRF tokens on sensitive endpoints enables attackers to inject malicious scripts that persist and execute when other users view affected content.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 bhoogterp Scheduled plugin is installedAccess your WordPress admin panel, navigate to Plugins > Installed Plugins, and search for 'bhoogterp Scheduled' or 'Scheduled' plugin. Note the installed version displayed.Affected if The plugin named 'bhoogterp Scheduled' is present in the plugins list.
-
Compare installed version against affected rangeSince no specific version range was provided, check the plugin's version number from the plugins page and monitor the WordPress plugin repository or vendor advisories for the specific vulnerable version range.Affected if Your installed version matches or falls within any vulnerable version range announced for CVE-2025-31375.
-
Inspect plugin admin forms for CSRF token presenceNavigate to the plugin settings pages in the WordPress admin. View the HTML source of any forms that perform state-changing actions (add/edit/delete scheduled tasks). Look for a hidden input field containing an 'nonce' or 'token' parameter.Affected if State-changing forms in the plugin lack a CSRF protection token/nonce field.
-
Test input fields for XSS vulnerabilityAccess the plugin's input fields (such as task names, descriptions, or schedule parameters). Attempt to inject a benign script tag like <script>alert('test')</script> into text inputs and save the form. Then view the saved content.Affected if Injected script content is stored and rendered without sanitization when viewing the scheduled task.
You are affected if the bhoogterp Scheduled plugin is installed, your version is within the vulnerable range, and the plugin lacks CSRF tokens on sensitive endpoints allowing stored XSS injection.
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 dataImplement anti-CSRF tokens on all state-changing endpoints and validate/sanitize all user inputs to prevent XSS injection.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31375 — 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-2025-31375 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