CVE-2026-57365
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Hitesh Chandwani reCAPTCHA (v2 & v3) for Asgaros Forum recaptcha-for-asgaros-forum allows DOM-Based XSS.This issue affects reCAPTCHA (v2 & v3) for Asgaros Forum: from n/a through <= 1.1.0.
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 confidenceDOM-Based XSS vulnerability in the reCAPTCHA (v2 & v3) for Asgaros Forum plugin allows attackers to inject malicious scripts through unsanitized user input that gets processed by client-side JavaScript and reflected in web pages.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Verify Asgaros Forum plugin installationNavigate to WordPress admin > Plugins and locate Asgaros Forum. Check the installed version number displayed there.Affected if The plugin is installed and the version is prior to any patched release (no patched version specified in advisory).
-
Confirm reCAPTCHA module is enabledGo to Asgaros Forum settings > reCAPTCHA section in WordPress admin panel. Verify if reCAPTCHA v2 or v3 is activated.Affected if reCAPTCHA is enabled - the vulnerability only affects environments where the reCAPTCHA feature is turned on.
-
Identify reCAPTCHA configuration fieldsAccess Asgaros Forum > reCAPTCHA settings page. Locate fields that accept user input such as site key, secret key, or theme selection.Affected if User-configurable reCAPTCHA settings exist and are populated with values that could be reflected in the DOM.
-
Inspect browser DOM for unsanitized outputView the frontend page with reCAPTCHA enabled. Right-click > Inspect > Console. Look for JavaScript errors or inspect the DOM around reCAPTCHA elements for any user-supplied values appearing without encoding.Affected if User input from reCAPTCHA fields appears in page source without proper HTML entity encoding.
-
Review reCAPTCHA JavaScript handlingCheck the plugin files (typically in wp-content/plugins/asgaros-forum/includes/) for reCAPTCHA-related JavaScript files. Look for functions that insert user input into the DOM using innerHTML or similar methods without sanitization.Affected if The plugin code uses unsanitized user input in DOM manipulation operations.
You are affected if Asgaros Forum with reCAPTCHA (v2 or v3) is installed and enabled, and user-supplied reCAPTCHA configuration values can be observed in the page DOM without proper encoding.
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 dataApply output encoding/sanitization to all user-controlled data before DOM insertion, or update to a patched version of the plugin once released.
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57365 — 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-57365 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