CVE-2013-1639

NONECVSS 0.0Trending — 3 sources updated this week

0.0

Opera before 12.13 does not send CORS preflight requests in all required cases, which allows remote attackers to bypass a CSRF protection mechanism via a crafted web site that triggers a CORS request.

CVSS v3: —
EG Score: 0.0(none)
EPSS: 28.6%
KEV: Not listed

Published

February 8, 2013

Last Modified

April 29, 2026

References (6)

cve@mitrehttp://lists.opensuse.org/opensuse-updates/2013-02/msg00038.html
cve@mitrehttp://www.opera.com/docs/changelogs/unified/1213/
cve@mitrehttp://www.opera.com/support/kb/view/1045/
af854a3a-2127-422b-91ae-364da2661108http://lists.opensuse.org/opensuse-updates/2013-02/msg00038.html
af854a3a-2127-422b-91ae-364da2661108http://www.opera.com/docs/changelogs/unified/1213/
af854a3a-2127-422b-91ae-364da2661108http://www.opera.com/support/kb/view/1045/

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-352Cross-Site Request Forgery (CSRF)

Data Freshness Timeline

(refreshed 15× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:10 UTCepss_batch
2026-06-02 20:10 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-29 01:02 UTCEG score recompute
2026-05-29 01:02 UTCGHSA enrichment
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 07:16 UTCepss_batch

Frequently asked(4)

What is CVE-2013-1639?

CVE-2013-1639 is a none vulnerability published on February 8, 2013. Opera before 12.13 does not send CORS preflight requests in all required cases, which allows remote attackers to bypass a CSRF protection mechanism via a crafted web site that triggers a CORS request.

When was CVE-2013-1639 disclosed?

CVE-2013-1639 was first published in the National Vulnerability Database on February 8, 2013, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2013-1639 actively exploited?

CVE-2013-1639 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 28.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

How do I remediate CVE-2013-1639?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-1639, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2013-1639

Explore →

Is Your Infrastructure Affected by CVE-2013-1639?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2013-1639

📅 Published

🔄 Last Modified

🔗 References (6)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(4)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2013-1639?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (6)

Frequently asked(4)

Related CVEs(same CWE)