Pre Orders For WoocommerceWordPress extension · Brightplugins
CVE-2023-46783
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 · uneditedAuth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Bright Plugins Pre-Orders for WooCommerce plugin <= 1.2.13 versions.
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 confidenceAuthenticated contributor+ stored XSS in the Pre-Orders for WooCommerce plugin allows injection of malicious JavaScript that persists in the database and executes when administrators or customers view pre-order related pages.
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
Pre Orders For WoocommerceWordPress extension
<= 1.2.13CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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.
-
Confirm plugin installation and versionNavigate to WordPress Admin > Plugins > Installed Plugins, locate 'Brightplugins Pre Orders For Woocommerce', and note the version number displayed. Alternatively, use WP-CLI: wp plugin list --name='pre-orders-for-woocommerce' --format=tableAffected if The installed version is 1.2.13 or lower (the version number appears next to the plugin name)
-
Verify plugin is activeIn the same plugins list, check if the plugin has an 'Active' status under the plugin name. Alternatively, use WP-CLI: wp plugin is-active pre-orders-for-woocommerceAffected if The plugin is active and running (inactive plugins cannot be exploited)
-
Check if pre-orders feature is enabledGo to WooCommerce > Settings > Pre-Orders (or similar plugin settings page), and look for options that enable pre-order functionality for products. Check if any products have pre-order status enabled.Affected if Pre-order functionality is enabled and products are configured for pre-orders (the XSS payload would be stored in pre-order data)
-
Inspect pre-order database entries for suspicious contentAccess the WordPress database (via phpMyAdmin or CLI). Examine tables related to pre-orders (commonly wp_posts with post_type like 'shop_order' or custom tables created by the plugin). Look for fields containing script tags, javascript:, or other XSS payloads in pre-order notes, customer information, or product metadata.Affected if Pre-order database entries contain unexpected HTML, script tags, or JavaScript event handlers (for example, <script>, onerror=, onload=, javascript:)
Your environment is affected if the Brightplugins Pre Orders For WooCommerce plugin versions 1.2.13 or below are active, pre-order functionality is enabled, and malicious scripts are present in pre-order database records.
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 Bright Plugins Pre-Orders for WooCommerce plugin to version 1.2.14 or later; alternatively, disable the plugin until a patched version is available.
Fix this in Pre Orders For Woocommerce
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46783 — 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-2023-46783 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