Business One PageWordPress extension · Rarathemes
CVE-2024-37505
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 Rara Themes Business One Page allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Business One Page: from n/a through 1.2.9.
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 confidenceMissing authorization vulnerability in the Rara Themes Business One Page WordPress theme allows attackers to bypass access control checks due to incorrectly configured security levels. The theme fails to properly validate user permissions before granting access to sensitive functionality or resources, enabling unauthorized users to perform actions beyond their intended privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Business One PageWordPress extension
< 1.3.0CVSS 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
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/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.
-
Identify the installed theme versionNavigate to Appearance > Themes in the WordPress admin dashboard and check the version listed for the Business One Page theme, or open the style.css file in the theme directory and look for the 'Version:' header commentAffected if The version displayed is less than 1.3.0 (e.g., 1.2.9, 1.2.8, etc.)
-
Locate theme PHP files with sensitive functionalityAccess the theme files via FTP or file manager and navigate to the wp-content/themes/business-one-page directory. Examine PHP files that handle admin functions, AJAX endpoints, or user-specific actionsAffected if The theme is version < 1.3.0 and contains PHP files with admin or user action handlers
-
Verify capability checks exist in theme functionsSearch the theme's PHP files (especially functions.php, admin files, and any files handling AJAX actions) for WordPress capability functions like 'current_user_can', 'check_admin_referer', or 'wp_verify_nonce'. Use a text search to see if these authorization functions are presentAffected if No capability checks (current_user_can) are found before sensitive operations, or authorization logic is missing entirely from key functions
A user is affected if the installed Business One Page theme version is below 1.3.0 AND the theme contains admin functions or sensitive operations that lack proper capability verification checks.
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 · scoped1.3.0
Implement proper role-based access control (RBAC) checks throughout the theme, verifying user permissions before executing sensitive operations. Ensure all admin functions and user-specific actions validate authorization tokens and capability requirements.
1.3.0
- Backup the entire WordPress site (database and files) before proceeding
- Navigate to WordPress dashboard > Appearance > Themes
- Deactivate the current Business One Page theme
- Delete the existing Business One Page theme (or keep a backup)
- Install Business One Page version 1.3.0 or later
- Activate the new version
- Verify the theme is functioning correctly and test that the authorization vulnerability is resolved
- Ensure all site functionality works as expected post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Business One Page
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37505 — 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-2024-37505 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