LiveActive security incident?Get immediate response
CVE Record

CVE-2022-25303: Cross-site Scripting (XSS)

The package whoogle-search before 0.7.2 are vulnerable to Cross-site Scripting (XSS) via the query string parameter q. In the case where it does not contain the http string, it is used to build the error_message that is then rendered in the error.html template, using the [flask.render_template](https://flask.palletsprojects.com/en/2.1.x/api/flask.render_template) function. However, the error_message is rendered using the [| safe filter](https://jinja.palletsprojects.com/en/3.1.x/templates/working-with-automatic-escaping), meaning the user input is not escaped.

MediumCVSS 5.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-25303 is a cross-site scripting flaw in whoogle-search before 0.7.2. A crafted search query can be reflected into an error page without proper escaping, potentially letting attacker-controlled browser script run when a user follows or submits the malicious query.

Executive priority

Schedule remediation for internet-facing or shared Whoogle instances. This is not a critical infrastructure bug, but it can support phishing, session abuse, or user data exposure if a trusted instance is vulnerable.

Technical view

The q query parameter can flow into error_message when it lacks the http string. That value is rendered in error.html through Flask/Jinja with the safe filter, bypassing automatic escaping. CVSS 3.1 is 5.4: network reachable, low complexity, no privileges, user interaction required, with limited confidentiality and integrity impact.

Likely exposure

Exposure is limited to deployments running whoogle-search versions before 0.7.2, especially public or shared instances where untrusted users can reach the search endpoint. The source bundle does not identify affected CPEs or deployment platforms.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires user interaction, such as a victim reaching a crafted query or error page. Impact is browser-side and may affect data visible to the user session.

Researcher notes

Evidence is strongest for the root cause and version boundary from the CVE/Snyk description and upstream code references. No exploit maturity beyond CVSS E:P and no active exploitation evidence is provided in the bundle.

Mitigation direction

  • Upgrade whoogle-search to version 0.7.2 or later where available.
  • Apply the referenced upstream fix if packaging is source-based.
  • Ensure user-controlled error messages are HTML-escaped before rendering.
  • Avoid marking query-derived template values as safe.
  • Limit public access to vulnerable instances until remediation is complete.

Validation and detection

  • Inventory whoogle-search deployments and record running versions.
  • Confirm vulnerable instances are older than 0.7.2.
  • Review error template rendering for safe use on query-derived text.
  • Use safe application testing to verify q input is escaped in error pages.
  • Check logs for unusual search URLs containing markup-like input.
Prepared
Confidence
high
Sources
5

Public sources used

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.

cve · low confidence lookup

CVE-2022-25303 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
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

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

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
4Source 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
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N/E:P2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2022-25303Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/awhoogle-searchunspecifiedListed
Weakness

CWE details

No CWE listed

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