CVE-2025-62934
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 Mejar WP Business Hours wp-business-hours allows Stored XSS.This issue affects WP Business Hours: from n/a through <= 1.4.
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 CSRF vulnerability in the WP Business Hours WordPress plugin (versions <=1.4) allows attackers to inject malicious JavaScript through Stored XSS. Attackers can trick authenticated administrators into submitting crafted requests that store malicious scripts in the plugin's business hours configuration, which then execute when other users view the affected pages.
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.
-
Check the WP Business Hours plugin versionLog into WordPress admin, go to Plugins > Installed Plugins, find 'WP Business Hours' and look at the version number displayed. Alternatively, check the main plugin file (wp-business-hours.php) header comment for the Version field.Affected if version number is 1.4 or lower
-
Verify the plugin is activeIn WordPress admin under Plugins > Installed Plugins, confirm that WP Business Hours shows as 'Active' rather than 'Inactive' or 'Must Use'.Affected if the plugin is currently active on the site
-
Inspect stored business hours configuration for malicious scriptsAccess the WordPress database (via phpMyAdmin or wp-cli), query the wp_options table for options containing 'business_hours' or the plugin's option name. Examine the stored value for any unexpected <script> tags, iframe elements, or encoded JavaScript patterns.Affected if the business hours configuration contains unrecognized script, iframe, or JavaScript code
-
Review the plugin settings page for stored XSSNavigate to the plugin's admin settings page (usually under Settings > Business Hours or a dedicated menu item). View the page source or inspect form fields to see if any business hours fields contain executable JavaScript when rendered.Affected if rendered business hours data displays unexpected script tags or executes JavaScript
-
Check admin activity logs for suspicious configuration changesIf available, review WordPress audit logs or plugin activity logs for recent changes to the WP Business Hours settings, looking for entries with unusual timestamps or associated with unexpected admin accounts.Affected if business hours settings were modified by an unrecognized admin account or outside normal operations
You are affected if WP Business Hours plugin version 1.4 or lower is active AND malicious script code is found stored in the plugin's business hours configuration or rendered on its settings pages.
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.
dbcve · scopedImplement anti-CSRF tokens (nonce validation) on all form submissions and admin actions, and apply proper input sanitization and output escaping for all user-supplied data before storage and display.
Version 1.5 or later (check WordPress plugin repository for latest release)
- 1. Navigate to the WordPress admin dashboard
- 2. Go to Plugins > Installed Plugins
- 3. Locate the WP Business Hours plugin (by Mejar)
- 4. Check if an update to version 1.5 or later is available
- 5. If available, update the plugin to the latest version
- 6. Verify the update was successful and the plugin is functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62934 — 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-62934 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