CVE-2026-22491
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 wphocus My auctions allegro my-auctions-allegro-free-edition allows Reflected XSS.This issue affects My auctions allegro: from n/a through <= 3.6.35.
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 confidenceA reflected Cross-Site Scripting (XSS) vulnerability exists in the wphocus My Auctions Allegro WordPress plugin (free edition, versions up to 3.6.35). The plugin fails to properly sanitize user-supplied input before reflecting it back in web pages, allowing attackers to inject malicious JavaScript code that executes in the context of victim users' browsers.
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.
-
Identify if the plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'My Auctions Allegro' by wphocus, or check the /wp-content/plugins/ directory for a folder named 'my-auctions-allegro' or similarAffected if The plugin is installed and active in WordPress
-
Check the installed version numberIn WordPress admin > Plugins, find My Auctions Allegro and view the version number displayed under the plugin name, or inspect the plugin's main PHP file for a 'Version' header in the plugin comment blockAffected if The version number is 3.6.35 or lower (versions up to 3.6.35 are affected)
-
Identify the plugin folder nameAccess the WordPress site via FTP or file manager and navigate to /wp-content/plugins/ to locate the exact folder name used by the plugin (may be 'my-auctions-allegro' or 'wphocus-my-auctions-allegro')Affected if The plugin folder exists indicating the vulnerable plugin is present
-
Inspect for reflected user inputExamine the plugin's PHP files for code that takes request parameters (GET/POST) and outputs them directly to HTML without sanitization functions like esc_html(), esc_attr(), or sanitize_text_field()Affected if User-supplied parameters are found being echoed directly to page output without proper escaping
-
Test the vulnerable endpointSubmit a test payload like <script>alert('XSS')</script> in URL parameters used by the plugin (such as search, filter, or ID parameters) and observe if the payload is reflected verbatim in the responseAffected if The submitted payload appears unmodified in the page source, confirming the XSS vulnerability exists
The environment is affected if the My Auctions Allegro plugin is installed with version 3.6.35 or lower and user input is reflected without sanitization in the plugin's output.
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 plugin to the latest version which includes proper input sanitization and output encoding, or apply the vendor patch if available. Implement context-aware output encoding for all user inputs before rendering in HTML.
- 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-22491 — 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-22491 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