CVE Tools

CVE-2022-31854

Public exploit available. Not confirmed exploited in the wild yet. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Check if you are running Codoforum v5.1 and whether admin accounts could be compromised or misused.
  2. Restrict admin panel access to trusted staff only and enforce strong, unique passwords plus two-factor authentication if available.
  3. Contact Codoforum (https://codoforum.com) to confirm whether a patched version beyond v5.1 is available and apply it.
  4. Until patched, review recently uploaded logo files and server directories for unfamiliar script files (e.g. .php, .jsp).
  5. Consider disabling or tightly monitoring the logo-change feature until a fix is confirmed installed.

What it is

From the CVE record

Codoforum v5.1 was discovered to contain an arbitrary file upload vulnerability via the logo change option in the admin panel.

In plain language

Written by AI from the record

If you run a Codoforum discussion forum, a malicious or compromised admin account could upload a hacking script through the logo-upload feature and take over your site; it's a real risk but only if someone already has admin access.

Codoforum v5.1 allows an authenticated administrator to achieve remote code execution via improper file-type validation (CWE-434) in the admin-panel logo-upload feature, enabling upload of executable scripts to the server.

If you're affected

  • Full website takeover
  • Malware/webshell hosting
  • Forum data exposure
  • Reputational damage from defacement

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS98th
Public exploit
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

2 sources with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

32% chance of exploitation activity in the next 30 days, which ranks it in the 98th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

The patch came 471 days before any public exploit.

  1. EPSS band changehigh → moderate
  2. Public exploit / PoCsource: github-pocnuclei check added
  3. Patch availablerecord updated
  4. Publishedweakness classified, att&ck mapped

Affected products

And 1 more affected product. See all after sign-in

Technical detail

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Scored 7.2 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required HighRequires admin or elevated privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Codoforum, not every advisory. This one: public exploit.