CVE-2025-46488
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 dastan800 Visual Builder visual-builder allows Reflected XSS.This issue affects Visual Builder: from n/a through <= 1.2.2.
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 in dastan800 Visual Builder plugin versions <=1.2.2 allows attackers to inject malicious scripts via reflected XSS. The CVSS 7.1 score indicates high severity due to the combination of user authentication bypass and script injection capability.
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 if dastan800 Visual Builder plugin is installedLocate the plugin files in the wp-content/plugins directory, looking for a folder named 'dastan800-visual-builder' or similar, or query the WordPress database wp_options table for the option_name containing 'active_plugins'Affected if The plugin folder or database entry exists on the system
-
Identify the installed plugin versionOpen the main plugin PHP file (usually index.php or the primary plugin file) and read the 'Version' header in the plugin comment block, or check the version entry in the WordPress plugins admin panelAffected if The version number returned is 1.2.2 or lower
-
Verify the plugin is active on the siteIn WordPress admin, navigate to Plugins > Installed Plugins and confirm the Visual Builder plugin shows as 'Active', or query the wp_active_plugins option in the databaseAffected if The plugin is activated and accessible to site visitors
-
Test for unauthenticated access to the vulnerable endpointSend a crafted HTTP GET request to common Visual Builder admin-ajax endpoints (such as ?action=visual_builder_get_data or similar reflected parameters) without providing authentication cookies or credentialsAffected if The endpoint responds without requiring authorization and reflects user input in the response without sanitization
If the plugin is installed, active, version 1.2.2 or lower, and the vulnerable reflected XSS endpoint is accessible without authentication, the environment is affected by CVE-2025-46488.
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 dataUpgrade to the latest version if available; otherwise implement proper authorization checks and output encoding/sanitization on all user-input reflected locations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46488 — 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-46488 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