CVE-2026-7462
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 · uneditedThe VatanSMS WP SMS plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the `page` parameter in all versions up to, and including, 1.01. This is due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick an administrator into performing an action such as clicking on a link.
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 · high confidenceThe VatanSMS WP SMS WordPress plugin is vulnerable to reflected cross-site scripting (XSS) via the `page` parameter due to insufficient input sanitization and output escaping. Unauthenticated attackers can inject arbitrary JavaScript that executes in an administrator's browser when tricked into clicking a malicious link.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify VatanSMS WP SMS plugin is installedNavigate to WordPress admin dashboard > Plugins and confirm 'VatanSMS WP SMS' or 'WP SMS' plugin is active. Alternatively, check the plugins directory: /wp-content/plugins/ for a folder containing 'vatan' or 'wp-sms' in the name.Affected if Plugin is installed and active
-
Check installed plugin versionIn WordPress admin > Plugins > Installed Plugins, find VatanSMS WP SMS and read the version number displayed below the plugin name. If not visible there, check the plugin's main PHP file header for 'Version:' tag.Affected if Version is 1.01 or any version up to and including 1.01
-
Identify if admin access is availableCheck if you have administrator-level access to the WordPress dashboard. XSS via this vulnerability requires an administrator to click a malicious URL.Affected if Administrator access exists and plugin is installed (admin could be targeted)
-
Confirm vulnerable parameter usageReview plugin source code for files handling the 'page' parameter, typically in admin menu or page routing logic. Look for $_GET['page'] being used without sanitize_text_field or esc_html/esc_attr when outputting to HTML.Affected if Code uses $_GET['page'] without proper sanitization and escaping before output
If the VatanSMS WP SMS plugin is installed at version 1.01 or below and the code processes the 'page' parameter without sanitization, the environment is affected by this reflected XSS vulnerability.
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 VatanSMS WP SMS plugin to version 1.02 or later which addresses the sanitization and output escaping issues; alternatively, implement proper sanitization of the `page` parameter using WordPress sanitization functions and output escaping before rendering.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7462 — 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-2026-7462 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