LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22491: WordPress My auctions allegro plugin <= 3.6.35 - Cross Site Scripting (XSS) vulnerability

Improper 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.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-22491 is a reflected cross-site scripting issue in the WordPress plugin My auctions allegro. An attacker could trick a user into opening a crafted link, causing script to run in that user’s browser. The listed severity is high, but the attack requires user interaction.

Executive priority

Treat this as a high-priority WordPress plugin issue for sites using My auctions allegro. It is not confirmed exploited, but XSS can support account abuse and content manipulation if users are targeted.

Technical view

The CVE describes CWE-79 improper input neutralization during web page generation in wphocus My auctions allegro, package my-auctions-allegro-free-edition. It affects versions through 3.6.35 per the CVE description. CVSS 3.1 is 7.1: AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L.

Likely exposure

Exposure is limited to WordPress sites with the My auctions allegro plugin installed at an affected version. The public bundle does not identify vulnerable parameters, pages, or whether authenticated users are needed; CVSS indicates no privileges required but user interaction is required.

Exploitation context

No CISA KEV listing is provided, and the sources do not state active exploitation. Practical exploitation would depend on persuading a user to visit a malicious link affecting a vulnerable WordPress site.

Researcher notes

The source data is sparse. The CVE description says through 3.6.35, while the Patchstack URL references 3.6.33. No vulnerable endpoint, proof of concept, patch version, or exploit-in-the-wild evidence is included in the provided sources.

Mitigation direction

  • Inventory WordPress sites for the My auctions allegro plugin.
  • Check the installed plugin version against the CVE’s affected range.
  • Review Patchstack and vendor guidance for an available fixed version.
  • If no fix is available, consider disabling the plugin until guidance is available.
  • Prioritize sites with public traffic or high-privilege WordPress users.

Validation and detection

  • Confirm whether my-auctions-allegro-free-edition is installed.
  • Record plugin version from WordPress administration or asset inventory.
  • Compare findings with the CVE stated affected range through 3.6.35.
  • Review web logs for unusual traffic to plugin-related pages.
  • Do not perform exploit testing without authorization and a safe test plan.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22491 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2026-22491Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
wphocusMy auctions allegromy-auctions-allegro-free-edition, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.