Skip to main content
CVE-2024-27563VulnerabilityPublished Updated

CVE-2024-27563: WonderCMS · n/a

Affects WonderCMSSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Mar 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
GitHubwondercms/WonderCMSpkg:github/wondercms/WonderCMSOther threatsAffected
  • =3.1.3
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Since no official patches are currently available, organizations should implement immediate mitigations to reduce exposure. These include: 1) Restricting outbound HTTP requests from the WonderCMS server using firewall rules or network segmentation to limit the server's ability to reach unauthorized internal or external endpoints. 2) Implementing input validation and sanitization at the application or web server level to block or filter suspicious pluginThemeUrl parameter values, such as disallowing private IP ranges or localhost addresses. 3) Monitoring and logging all outbound requests initiated by the CMS to detect anomalous or unexpected traffic patterns indicative of SSRF exploitation attempts. 4) Employing web application firewalls (WAFs) with custom rules to detect and block SSRF attack patterns targeting the pluginThemeUrl parameter. 5) Isolating the WonderCMS environment in a restricted network zone with minimal privileges to limit the impact of potential exploitation. 6) Staying updated with WonderCMS vendor advisories for official patches or updates addressing this vulnerability and applying them promptly once released. 7) Conducting regular security assessments and penetration testing focused on SSRF and related vulnerabilities in the CMS environment.

Description

A Server-Side Request Forgery (SSRF) in the getFileFromRepo function of WonderCMS v3.1.3 allows attackers to force the application to make arbitrary requests via injection of crafted URLs into the pluginThemeUrl parameter.

References

Community reviews

Loading reviews…