LiveActive security incident?Get immediate response
CVE Record

CVE-2022-36262: An issue was discovered in taocms 3.0.2.

An issue was discovered in taocms 3.0.2. in the website settings that allows arbitrary php code to be injected by modifying config.php.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-36262 concerns taocms 3.0.2. The reported issue allows PHP code to be injected through website settings by modifying config.php. If reachable by an attacker, this could let them run code in the CMS environment. The public data does not provide a CVSS score, patch status, or confirmed exploitation.

Executive priority

Prioritize review if taocms is internet-facing or used on business-critical sites. The potential impact is serious, but urgency depends on whether taocms 3.0.2 is present and who can access website settings.

Technical view

The source description identifies arbitrary PHP code injection in taocms 3.0.2 through configuration modification of config.php from website settings. The bundle does not specify authentication requirements, exact vulnerable parameters, affected ranges beyond 3.0.2, CWE, or vendor remediation. Treat impact as potentially server-side code execution, but validate against local deployment behavior.

Likely exposure

Exposure is likely limited to organizations running taocms 3.0.2, especially where the website settings function is accessible to untrusted or compromised users. The provided affected metadata is incomplete and does not define broader product or version ranges.

Exploitation context

The CVE is not marked as CISA KEV in the bundle. Public GitHub references exist, but the provided sources do not establish active exploitation, a working exploit, or exploit maturity. Evidence is incomplete.

Researcher notes

Key gaps are authentication context, exact injection vector, vulnerable code path, affected version range, and remediation status. Avoid assuming unauthenticated exploitation. Validate from the referenced GitHub issue and local source before assigning exploitability.

Mitigation direction

  • Check the taocms repository and issue for vendor guidance or fixed versions.
  • Restrict access to taocms administrative and website settings functions.
  • Review config.php permissions and prevent unnecessary web-user write access.
  • Audit config.php for unauthorized PHP changes.
  • Plan upgrade, replacement, or compensating controls if no maintained fix exists.

Validation and detection

  • Inventory systems for taocms 3.0.2 installations.
  • Confirm whether website settings can modify config.php in production.
  • Review access controls for settings and administrative users.
  • Inspect config.php history and current contents for unauthorized changes.
  • Check web and admin logs for suspicious settings changes.
Prepared
Confidence
medium
Sources
5

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-36262 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
1ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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