Security readout for executives and security teams
Plain-English summary
A critical flaw in Phoca Cart can let an unauthenticated internet user manipulate database queries through public product-filter inputs. Successful abuse could expose or alter the store database and disrupt availability. Sites running affected versions with the public shop items page reachable should treat this as urgent.
Executive priority
Treat internet-facing affected stores as an immediate remediation priority because compromise requires no account or user action and may affect customer, order, or operational data. Confirm exposure now, preserve evidence, and follow current vendor guidance. The supplied sources do not name a patched version, workaround, or exploitation campaign.
Technical view
CVE-2026-74251 is a CWE-89 SQL injection in Phoca Cart 5.0.0 through 6.1.6. The public shop items page reportedly concatenates the a[] attribute and s[] specification GET parameters into SQL WHERE clauses without parameterization or escaping. The record describes arbitrary SQL injection and database extraction through time-based blind behavior.
Likely exposure
Exposure is most likely where Phoca Cart 5.0.0 through 6.1.6 is installed and its public shop items page is internet-accessible. The supplied record does not identify affected URLs, configurations, CPEs, or whether every installation exposes the vulnerable filtering path.
Exploitation context
The CVSS 4.0 score is 9.3, reflecting remote, low-complexity, unauthenticated exploitation without user interaction and potentially high confidentiality, integrity, and availability impact. The source bundle marks KEV as false and provides no evidence of active exploitation. That absence does not establish that exploitation is not occurring.
Researcher notes
The key reported sink is raw construction of SQL WHERE conditions from array-valued GET inputs. The description specifically identifies time-based blind extraction, but the supplied public material does not provide code-level evidence, affected route details, prerequisites, patch analysis, or a vendor security advisory. Avoid intrusive production testing; validate through version, reachability, logs, and authorized review.
Mitigation direction
- Inventory Joomla sites and identify every installed Phoca Cart version.
- Check current Phoca guidance for a fixed release or vendor-approved mitigation.
- Prioritize vendor-directed remediation for internet-facing versions 5.0.0 through 6.1.6.
- Until remediated, consider restricting access to the affected public filtering functionality.
- Preserve relevant web and database logs before making containment changes.
Validation and detection
- Confirm the installed Phoca Cart version from authoritative deployment or package records.
- Determine whether the public shop items page and filtering parameters are externally reachable.
- Review logs for unusual, repeated, or timing-correlated requests involving a[] or s[] parameters.
- Investigate database access anomalies and unexpected changes associated with the Joomla application account.
- After remediation, verify the installed version against current Phoca guidance and recheck exposure safely.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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 lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-74251 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——JoomlaVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.phoca.cz/phocacartCVE reference, Joomla · product
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command
Improper Neutralization of Special Elements used in an SQL Command represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.