CVE-2026-105225 osCommerce CVE debrief

Who should care

Defenders responsible for osCommerce osCommerce2 installations, especially those with publicly accessible payment pages, should assess the vulnerability status and potential exposure to code injection attacks.

Why it matters

Defenders should prioritize verifying the vulnerability status of osCommerce osCommerce2 installations, especially those with publicly accessible payment pages, and assess the feasibility of code injection attacks. The exploit is publicly available, but there is no evidence of active exploitation.

• Verification of osCommerce osCommerce2 installations for vulnerability to code injection attacks
• Assessment of remote code injection attack feasibility on publicly accessible payment pages
• Monitoring for potential exploitation attempts

Technical summary

The vulnerability affects the function include of the file includes/classes/payment.php of the component Payment Page in osCommerce osCommerce2 up to 2.3.4.1. Manipulation of the argument MODULE_PAYMENT_INSTALLED leads to code injection. The attack can be executed remotely. Defenders should prioritize verifying the vulnerability status of osCommerce osCommerce2 installations, especially those with publicly accessible payment pages, and assess the feasibility of code injection attacks. The exploit is publicly available, but there is no evidence of active exploitation.

Defensive priority

Defenders should prioritize verifying the vulnerability status of osCommerce osCommerce2 installations, especially those with publicly accessible payment pages, and assess the feasibility of code injection attacks.

Recommended defensive actions

• Verify osCommerce osCommerce2 installations for vulnerability to code injection attacks
• Assess the feasibility of remote code injection attacks on publicly accessible payment pages
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide limited information about the vulnerability. The exploit is publicly available, but there is no evidence of active exploitation. Defenders should verify the vulnerability status of osCommerce osCommerce2 installations, especially those with publicly accessible payment pages, and assess the feasibility of code injection attacks. The CVE record was published on 2026-10-05T05:17:02.900Z and has not been modified since then. The information is based on the available data and might not be comprehensive.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.