Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-56281: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')

0
Unknown
VulnerabilityCVE-2024-56281cvecve-2024-56281
Published: Tue Jan 07 2025 (01/07/2025, 10:49:21 UTC)
Source: CVE Database V5
Vendor/Project: codemstory

Description

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in codemstory 워드프레스 결제 심플페이 pgall-for-woocommerce allows PHP Local File Inclusion.This issue affects 워드프레스 결제 심플페이: from n/a through <= 5.2.0.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/02/2026, 09:57:34 UTC

Technical Analysis

CVE-2024-56281 is a Local File Inclusion (LFI) vulnerability found in the codemstory 워드프레스 결제 심플페이 pgall-for-woocommerce WordPress plugin, affecting versions up to 5.2.0. The vulnerability arises from improper control and validation of the filename parameter used in PHP include or require statements. This flaw allows an attacker to manipulate the filename input to include arbitrary local files on the web server. By exploiting this, an attacker can read sensitive files such as configuration files, password files, or other application data, potentially leading to information disclosure or further code execution if combined with other vulnerabilities. The vulnerability is classified as a PHP Remote File Inclusion type but specifically manifests as Local File Inclusion due to the nature of the flaw. No CVSS score is currently assigned, and no known exploits have been observed in the wild. The plugin is used in WordPress environments, primarily targeting e-commerce payment processing in Korean language contexts. The root cause is insufficient input validation and sanitization in the plugin's code handling file inclusion. This vulnerability highlights the risks of dynamic file inclusion without strict controls in PHP applications, especially in widely used CMS plugins.

Potential Impact

The impact of CVE-2024-56281 can be significant for organizations using the affected WordPress plugin. Successful exploitation can lead to unauthorized disclosure of sensitive server files, including credentials, configuration files, or other critical data. This can facilitate further attacks such as privilege escalation, remote code execution, or full server compromise if combined with other vulnerabilities. For e-commerce sites, this could result in exposure of customer data, payment information, and disruption of payment processing services, damaging reputation and causing financial losses. The scope is limited to sites using the vulnerable plugin, but given WordPress's large market share and the plugin's focus on payment processing, the affected attack surface is non-trivial. Although no public exploits are currently known, the vulnerability's nature makes it a high-value target for attackers seeking to gain initial access or escalate privileges. The lack of authentication requirement or user interaction details is not specified, but typically such LFI vulnerabilities can be exploited remotely if the vulnerable endpoint is accessible.

Mitigation Recommendations

To mitigate CVE-2024-56281, organizations should immediately check if they are running the affected versions (<= 5.2.0) of the codemstory 워드프레스 결제 심플페이 pgall-for-woocommerce plugin. They should apply any available patches or updates from the vendor as soon as they are released. In the absence of an official patch, manual mitigation includes reviewing and modifying the plugin code to enforce strict validation and sanitization of any input used in include or require statements, ensuring only allowed filenames or paths are accepted. Implementing a whitelist approach for file inclusion parameters is recommended. Additionally, web application firewalls (WAFs) can be configured to detect and block suspicious requests attempting directory traversal or file inclusion patterns. Regularly auditing server logs for unusual access patterns and restricting file permissions on the server to limit access to sensitive files can reduce exploitation impact. Finally, organizations should maintain regular backups and monitor for indicators of compromise related to this vulnerability.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2024-12-18T19:04:43.976Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69cd75cfe6bfc5ba1df07d3b

Added to database: 4/1/2026, 7:45:19 PM

Last enriched: 4/2/2026, 9:57:34 AM

Last updated: 4/6/2026, 9:18:07 AM

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses