Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-77999 – Unauthenticated Payment Fraud via PayPal IPN Forgery – J2Store Joomla Extension 1.0

Be the first to know when new zero-days emerge:

Summary

CVE-2026-77999 is a critical logic flaw in the J2Store Joomla e-commerce extension’s PayPal payment-confirmation handling. An unauthenticated attacker can forge PayPal Instant Payment Notification (IPN) callbacks to fraudulently move orders to a "CONFIRMED" state without making any payment, or to force legitimate pending orders into a "FAILED" state. The issue carries a CVSS score of 8.7 (High) and affects multiple major J2Store release lines.

Technical details

  • Root cause: The IPN signature-check function (_validateIPN()) treated any non-INVALID response — including PayPal’s UNVERIFIED response — as a valid confirmation, and made its verification request to PayPal with CURLOPT_SSL_VERIFYPEER disabled. The verdict it produced was stored in a field that no downstream code ever inspected, so order processing continued regardless of the actual verification result.
  • Amount-check bypass: The paid-amount comparison only executed when the mc_gross POST field was a positive number; omitting mc_gross from the forged POST body caused floatval(null) to evaluate to 0, silently skipping the check.
  • PayPal v2 gap: The separate paypalv2.php payment handler performed no amount validation at all, under any circumstance.
  • Trigger conditions: An attacker needs only the store’s configured receiver_email (merchant PayPal address, often discoverable) and a sequential, enumerable order ID passed via the custom field.
  • Attack vector: A single anonymous, unauthenticated HTTP POST request to the store’s PayPal IPN listener endpoint — no user interaction or session required.
  • Impact: Confirmation of orders without payment (financial fraud/theft of goods or services), or denial-of-service against legitimate customers’ orders by forcing them to a failed state.

Affected software

  • J2Store extension for Joomla, versions 1.0.0 through 3.3.21
  • J2Store extension for Joomla, versions 4.0.0 through 4.0.21
  • J2Store extension for Joomla, versions 4.1.0 through 4.1.6

Severity

CVSS v4.0 Base Score: 8.7 (High)
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade J2Store to a release beyond 4.1.6, where the affected versions are no longer listed as vulnerable. Confirm with the vendor (j2commerce.com) that the installed build addresses IPN signature validation, SSL peer verification, and amount checks described above.
  • If no patch is available:
    • Disable or restrict access to the PayPal IPN/notification endpoint until patched.
    • Manually enforce server-side verification of PayPal IPN responses (require an INVALID/VERIFIED check with SSL peer verification enabled) via custom code or a WAF rule that rejects IPN POSTs without a verifiable mc_gross value.
    • Monitor order status transitions for anomalies (e.g., orders confirmed without corresponding PayPal transaction records) and reconcile against PayPal merchant account activity.
    • Avoid exposing predictable/sequential order IDs where possible.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw HTTP response body: /media/j2store/, /components/com_j2store/

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge