Twitter API credential disclosure via hard-coded fallbacks
Published Sep 30, 2023 · Updated Sep 23, 2024
Hard-coded credentials in Microweber before 2.0 allow remote attackers to obtain four bundled Twitter OAuth credentials. The twitter_feed_perform_api_request function assigns embedded access-token, token-secret, consumer-key, and consumer-secret values whenever callers omit them. The published source exposes these values without product authentication, with the reported consequence limited to confidentiality of the associated Twitter account.
Summary
What happened
Hard-coded credentials in Microweber before 2.0 allow remote attackers to obtain four bundled Twitter OAuth credentials. The twitter_feed_perform_api_request function assigns embedded access-token, token-secret, consumer-key, and consumer-secret values whenever callers omit them. The published source exposes these values without product authentication, with the reported consequence limited to confidentiality of the associated Twitter account.
The record
- CVE
- CVE-2023-5318
- Published
- Sep 30, 2023
- Updated
- Sep 23, 2024
- Vendor
- Microweber
- Product
- Microweber
- Classifications
- CWE-798, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 30, 2023CVE publishedPublication date reported by the CVE source.
- Sep 23, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <2.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream credential-removal diffproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo