CVE-2026-1261
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 MetForm Pro plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Quiz feature in all versions up to, and including, 3.9.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 MetForm Pro WordPress plugin contains a stored Cross-Site Scripting vulnerability in its Quiz feature. Due to insufficient input sanitization of user-supplied data and inadequate output escaping when rendering quiz content, unauthenticated attackers can inject malicious JavaScript that persists on affected pages and executes when users access them.
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
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 MetForm Pro plugin is installedIn WordPress admin, navigate to Plugins > Installed Plugins and locate MetForm Pro in the list. Note the displayed version number.Affected if MetForm Pro plugin is present in the WordPress installation
-
Verify the Quiz feature is activeCheck if any quiz forms have been created using MetForm. Navigate to MetForm > All Forms and review for forms with quiz functionality, or inspect page content where quiz forms may be embedded.Affected if Quiz forms created with MetForm are published and accessible on the site
-
Inspect quiz form submissions for potential malicious contentAccess the WordPress database or MetForm entries for quiz forms. Review stored responses in fields that accept user input (such as quiz answers, participant names, or custom fields) for unusual characters or script tags.Affected if Quiz form entries contain unsanitized HTML or JavaScript tags like <script>, javascript:, or event handlers such as onload/onerror
-
Review published quiz pages in the browserVisit pages containing MetForm quiz elements. Right-click and view page source, or use browser developer tools to inspect the rendered HTML around quiz form fields for unescaped user-supplied data.Affected if User-supplied data in quiz responses appears as raw HTML or contains executable script content when viewed in the page source
A site is affected if MetForm Pro is installed with quiz functionality enabled and quiz form entries contain injected scripts that render unescaped in the page HTML.
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 MetForm Pro to version 3.9.7 or later which contains proper input sanitization and output escaping for the Quiz feature. Until then, consider disabling the Quiz feature or restricting access if possible.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1261 — 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-1261 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