CVE Intelligence
Skip to main content
MEDIUM

CVE-2022-0578

CVE-2022-0578 — Code Injection in publify/publify

Code Injection in GitHub repository publify/publify prior to 9.2.8.

Published Updated Sources: cvelistV5, @huntrdev

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

1%

chance of exploitation in 30 days

Affects

publify

publify_publify

CVSS base

5.3

MEDIUM

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

publify

Products (1)

publify publify

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
5.3CVSS 3.0MEDIUM——cvelistV5

Weakness & attack patterns

  • CWE-94

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1027.006Obfuscated Files or Information: HTML Smuggling
  • T1027.009Obfuscated Files or Information: Embedded Payloads
  • T1564.009Hide Artifacts: Resource Forking

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Search application, proxy, and WAF logs for requests touching /publify.

References

2 on the record

Elsewhere on this site

  • publifyevery CVE for this vendor
  • CWE-94other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.